Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: Korea Republic of

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 61.34.40.253
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 7416
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;61.34.40.253.			IN	A

;; AUTHORITY SECTION:
.			595	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2020050800 1800 900 604800 86400

;; Query time: 97 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri May 08 19:40:07 CST 2020
;; MSG SIZE  rcvd: 116
Host info
Host 253.40.34.61.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 253.40.34.61.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
119.61.6.131 attackspambots
PostgreSQL port 5432
2019-11-01 22:58:45
113.104.251.104 attackbotsspam
Nov  1 12:25:55 reporting7 sshd[26616]: Did not receive identification string from 113.104.251.104
Nov  1 12:31:08 reporting7 sshd[28704]: Invalid user admin from 113.104.251.104
Nov  1 12:31:08 reporting7 sshd[28704]: Failed password for invalid user admin from 113.104.251.104 port 16987 ssh2
Nov  1 12:32:14 reporting7 sshd[29376]: Invalid user ubuntu from 113.104.251.104
Nov  1 12:32:14 reporting7 sshd[29376]: Failed password for invalid user ubuntu from 113.104.251.104 port 17307 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=113.104.251.104
2019-11-01 23:16:32
2a00:23c6:4c0c:7b00:3d66:ee7f:9727:8141 attackspambots
ENG,WP GET /wp-login.php
2019-11-01 23:02:58
101.251.72.205 attackbotsspam
Nov  1 12:51:38 fr01 sshd[16383]: Invalid user magalie from 101.251.72.205
Nov  1 12:51:38 fr01 sshd[16383]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.251.72.205
Nov  1 12:51:38 fr01 sshd[16383]: Invalid user magalie from 101.251.72.205
Nov  1 12:51:41 fr01 sshd[16383]: Failed password for invalid user magalie from 101.251.72.205 port 48242 ssh2
...
2019-11-01 22:34:45
167.71.83.32 attackspambots
Digital Ocean BotNet attack - 10s of requests to none existent pages - :443/app-ads.txt - typically bursts of 8 requests per second - undefined, XSS attacks
node-superagent/4.1.0
2019-11-01 22:32:02
103.139.45.67 attackspam
Too many connections or unauthorized access detected from Yankee banned ip
2019-11-01 23:16:59
118.89.156.217 attackbotsspam
Invalid user antonio from 118.89.156.217 port 51232
2019-11-01 22:55:15
200.105.215.18 attackbotsspam
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/200.105.215.18/ 
 
 BO - 1H : (2)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : BO 
 NAME ASN : ASN26210 
 
 IP : 200.105.215.18 
 
 CIDR : 200.105.215.0/24 
 
 PREFIX COUNT : 179 
 
 UNIQUE IP COUNT : 57344 
 
 
 ATTACKS DETECTED ASN26210 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-11-01 12:50:49 
 
 INFO :  HACK ! - Looking for resource vulnerabilities Scan Detected and Blocked by ADMIN  - data recovery
2019-11-01 23:12:16
49.64.38.126 attack
Nov  1 12:30:54 mxgate1 postfix/postscreen[21104]: CONNECT from [49.64.38.126]:56101 to [176.31.12.44]:25
Nov  1 12:30:54 mxgate1 postfix/dnsblog[21241]: addr 49.64.38.126 listed by domain zen.spamhaus.org as 127.0.0.11
Nov  1 12:30:54 mxgate1 postfix/dnsblog[21241]: addr 49.64.38.126 listed by domain zen.spamhaus.org as 127.0.0.4
Nov  1 12:30:54 mxgate1 postfix/dnsblog[21239]: addr 49.64.38.126 listed by domain cbl.abuseat.org as 127.0.0.2
Nov  1 12:31:00 mxgate1 postfix/postscreen[21104]: DNSBL rank 3 for [49.64.38.126]:56101
Nov x@x
Nov  1 12:31:01 mxgate1 postfix/postscreen[21104]: HANGUP after 0.97 from [49.64.38.126]:56101 in tests after SMTP handshake
Nov  1 12:31:01 mxgate1 postfix/postscreen[21104]: DISCONNECT [49.64.38.126]:56101
Nov  1 12:31:01 mxgate1 postfix/postscreen[21104]: CONNECT from [49.64.38.126]:56243 to [176.31.12.44]:25
Nov  1 12:31:01 mxgate1 postfix/dnsblog[21240]: addr 49.64.38.126 listed by domain zen.spamhaus.org as 127.0.0.4
Nov  1 12:31:01........
-------------------------------
2019-11-01 23:14:09
41.210.128.37 attackspam
5x Failed Password
2019-11-01 22:59:44
49.234.28.54 attackbotsspam
Nov  1 03:55:30 web1 sshd\[32506\]: Invalid user serverpilot from 49.234.28.54
Nov  1 03:55:30 web1 sshd\[32506\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.28.54
Nov  1 03:55:32 web1 sshd\[32506\]: Failed password for invalid user serverpilot from 49.234.28.54 port 39094 ssh2
Nov  1 04:00:34 web1 sshd\[514\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.28.54  user=root
Nov  1 04:00:36 web1 sshd\[514\]: Failed password for root from 49.234.28.54 port 56556 ssh2
2019-11-01 22:32:53
165.22.112.87 attackspambots
$f2bV_matches
2019-11-01 22:48:51
167.172.82.230 attackbotsspam
Lines containing failures of 167.172.82.230
Oct 31 06:46:45 zabbix sshd[79640]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.82.230  user=r.r
Oct 31 06:46:47 zabbix sshd[79640]: Failed password for r.r from 167.172.82.230 port 47148 ssh2
Oct 31 06:46:47 zabbix sshd[79640]: Received disconnect from 167.172.82.230 port 47148:11: Bye Bye [preauth]
Oct 31 06:46:47 zabbix sshd[79640]: Disconnected from authenticating user r.r 167.172.82.230 port 47148 [preauth]
Oct 31 07:04:24 zabbix sshd[81004]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.82.230  user=r.r
Oct 31 07:04:26 zabbix sshd[81004]: Failed password for r.r from 167.172.82.230 port 42114 ssh2
Oct 31 07:04:27 zabbix sshd[81004]: Received disconnect from 167.172.82.230 port 42114:11: Bye Bye [preauth]
Oct 31 07:04:27 zabbix sshd[81004]: Disconnected from authenticating user r.r 167.172.82.230 port 42114 [preauth]
Oct 3........
------------------------------
2019-11-01 22:57:19
194.247.27.65 attackspam
slow and persistent scanner
2019-11-01 23:12:39
113.247.222.5 attackbots
Nov  1 09:11:50 lvpxxxxxxx88-92-201-20 sshd[2836]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.247.222.5  user=r.r
Nov  1 09:11:52 lvpxxxxxxx88-92-201-20 sshd[2836]: Failed password for r.r from 113.247.222.5 port 53446 ssh2
Nov  1 09:11:53 lvpxxxxxxx88-92-201-20 sshd[2836]: Received disconnect from 113.247.222.5: 11: Bye Bye [preauth]
Nov  1 09:39:53 lvpxxxxxxx88-92-201-20 sshd[3196]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.247.222.5  user=r.r
Nov  1 09:39:55 lvpxxxxxxx88-92-201-20 sshd[3196]: Failed password for r.r from 113.247.222.5 port 58781 ssh2
Nov  1 09:39:55 lvpxxxxxxx88-92-201-20 sshd[3196]: Received disconnect from 113.247.222.5: 11: Bye Bye [preauth]
Nov  1 09:52:14 lvpxxxxxxx88-92-201-20 sshd[3370]: Failed password for invalid user teamspeak from 113.247.222.5 port 43523 ssh2
Nov  1 09:52:15 lvpxxxxxxx88-92-201-20 sshd[3370]: Received disconnect from 113.247........
-------------------------------
2019-11-01 22:59:18

Recently Reported IPs

193.234.25.180 138.156.177.4 21.146.116.173 75.102.76.237
209.72.173.229 51.43.255.51 103.143.170.137 148.213.231.207
155.135.147.115 77.42.122.191 193.142.146.30 58.255.109.84
34.210.61.223 66.245.212.137 30.194.212.186 98.183.99.199
209.130.163.33 154.85.32.123 206.114.160.52 165.22.252.109