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: IANA Special-Purpose Address

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 <<>> 253.20.45.140
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38137
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;253.20.45.140.			IN	A

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

;; Query time: 41 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 21 23:53:43 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 140.45.20.253.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 140.45.20.253.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
202.138.224.4 attackbots
2019-09-19T11:54:51.119921+01:00 suse sshd[19609]: Invalid user admin from 202.138.224.4 port 31209
2019-09-19T11:54:54.665415+01:00 suse sshd[19609]: error: PAM: User not known to the underlying authentication module for illegal user admin from 202.138.224.4
2019-09-19T11:54:51.119921+01:00 suse sshd[19609]: Invalid user admin from 202.138.224.4 port 31209
2019-09-19T11:54:54.665415+01:00 suse sshd[19609]: error: PAM: User not known to the underlying authentication module for illegal user admin from 202.138.224.4
2019-09-19T11:54:51.119921+01:00 suse sshd[19609]: Invalid user admin from 202.138.224.4 port 31209
2019-09-19T11:54:54.665415+01:00 suse sshd[19609]: error: PAM: User not known to the underlying authentication module for illegal user admin from 202.138.224.4
2019-09-19T11:54:54.666374+01:00 suse sshd[19609]: Failed keyboard-interactive/pam for invalid user admin from 202.138.224.4 port 31209 ssh2
...
2019-09-19 21:03:47
45.224.105.40 attackspam
2019-09-19T11:54:37.471028+01:00 suse sshd[19594]: Invalid user admin from 45.224.105.40 port 33330
2019-09-19T11:54:40.387519+01:00 suse sshd[19594]: error: PAM: User not known to the underlying authentication module for illegal user admin from 45.224.105.40
2019-09-19T11:54:37.471028+01:00 suse sshd[19594]: Invalid user admin from 45.224.105.40 port 33330
2019-09-19T11:54:40.387519+01:00 suse sshd[19594]: error: PAM: User not known to the underlying authentication module for illegal user admin from 45.224.105.40
2019-09-19T11:54:37.471028+01:00 suse sshd[19594]: Invalid user admin from 45.224.105.40 port 33330
2019-09-19T11:54:40.387519+01:00 suse sshd[19594]: error: PAM: User not known to the underlying authentication module for illegal user admin from 45.224.105.40
2019-09-19T11:54:40.388971+01:00 suse sshd[19594]: Failed keyboard-interactive/pam for invalid user admin from 45.224.105.40 port 33330 ssh2
...
2019-09-19 21:08:32
210.212.162.140 attack
Attempt to attack host OS, exploiting network vulnerabilities, on 19-09-2019 11:56:00.
2019-09-19 20:50:06
138.197.146.132 attackbots
CA hacking
2019-09-19 21:33:21
116.203.218.159 attackbotsspam
Sep 19 13:45:49 nginx sshd[45007]: Connection from 116.203.218.159 port 39588 on 10.23.102.80 port 22
Sep 19 13:45:49 nginx sshd[45007]: Received disconnect from 116.203.218.159 port 39588:11: Normal Shutdown, Thank you for playing [preauth]
2019-09-19 20:59:29
60.220.230.21 attack
Sep 19 08:37:13 ny01 sshd[1657]: Failed password for root from 60.220.230.21 port 48655 ssh2
Sep 19 08:42:08 ny01 sshd[2477]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.220.230.21
Sep 19 08:42:10 ny01 sshd[2477]: Failed password for invalid user sysadmin from 60.220.230.21 port 40537 ssh2
2019-09-19 20:50:38
184.68.96.62 attack
Attempt to attack host OS, exploiting network vulnerabilities, on 19-09-2019 11:55:24.
2019-09-19 21:25:02
46.0.203.166 attack
2019-09-19T08:46:11.4004351495-001 sshd\[25976\]: Invalid user zaq12wsx from 46.0.203.166 port 56960
2019-09-19T08:46:11.4082681495-001 sshd\[25976\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.0.203.166
2019-09-19T08:46:13.6894171495-001 sshd\[25976\]: Failed password for invalid user zaq12wsx from 46.0.203.166 port 56960 ssh2
2019-09-19T08:50:29.6260991495-001 sshd\[26165\]: Invalid user 111111 from 46.0.203.166 port 44024
2019-09-19T08:50:29.6333441495-001 sshd\[26165\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.0.203.166
2019-09-19T08:50:31.3323711495-001 sshd\[26165\]: Failed password for invalid user 111111 from 46.0.203.166 port 44024 ssh2
...
2019-09-19 21:01:48
58.42.206.175 attackbots
Sep 19 12:54:07 xeon cyrus/imap[63907]: badlogin: [58.42.206.175] plain [SASL(-13): authentication failure: Password verification failed]
2019-09-19 20:56:10
186.22.139.238 attackbotsspam
Attempt to attack host OS, exploiting network vulnerabilities, on 19-09-2019 11:55:38.
2019-09-19 21:09:12
217.66.30.136 attackspam
2019-09-19T11:54:13.971852+01:00 suse sshd[19572]: Invalid user admin from 217.66.30.136 port 29030
2019-09-19T11:54:16.354740+01:00 suse sshd[19572]: error: PAM: User not known to the underlying authentication module for illegal user admin from 217.66.30.136
2019-09-19T11:54:13.971852+01:00 suse sshd[19572]: Invalid user admin from 217.66.30.136 port 29030
2019-09-19T11:54:16.354740+01:00 suse sshd[19572]: error: PAM: User not known to the underlying authentication module for illegal user admin from 217.66.30.136
2019-09-19T11:54:13.971852+01:00 suse sshd[19572]: Invalid user admin from 217.66.30.136 port 29030
2019-09-19T11:54:16.354740+01:00 suse sshd[19572]: error: PAM: User not known to the underlying authentication module for illegal user admin from 217.66.30.136
2019-09-19T11:54:16.356384+01:00 suse sshd[19572]: Failed keyboard-interactive/pam for invalid user admin from 217.66.30.136 port 29030 ssh2
...
2019-09-19 21:24:11
201.234.52.222 attackspambots
Attempt to attack host OS, exploiting network vulnerabilities, on 19-09-2019 11:55:51.
2019-09-19 20:58:40
197.44.227.179 attackbotsspam
2019-09-19T11:53:54.331520+01:00 suse sshd[19556]: User root from 197.44.227.179 not allowed because not listed in AllowUsers
2019-09-19T11:53:57.382940+01:00 suse sshd[19556]: error: PAM: Authentication failure for illegal user root from 197.44.227.179
2019-09-19T11:53:54.331520+01:00 suse sshd[19556]: User root from 197.44.227.179 not allowed because not listed in AllowUsers
2019-09-19T11:53:57.382940+01:00 suse sshd[19556]: error: PAM: Authentication failure for illegal user root from 197.44.227.179
2019-09-19T11:53:54.331520+01:00 suse sshd[19556]: User root from 197.44.227.179 not allowed because not listed in AllowUsers
2019-09-19T11:53:57.382940+01:00 suse sshd[19556]: error: PAM: Authentication failure for illegal user root from 197.44.227.179
2019-09-19T11:53:57.387832+01:00 suse sshd[19556]: Failed keyboard-interactive/pam for invalid user root from 197.44.227.179 port 54305 ssh2
...
2019-09-19 21:35:45
189.115.42.72 attackspambots
Attempt to attack host OS, exploiting network vulnerabilities, on 19-09-2019 11:55:48.
2019-09-19 21:04:48
202.47.33.233 attackspam
Attempt to attack host OS, exploiting network vulnerabilities, on 19-09-2019 11:55:52.
2019-09-19 20:52:47

Recently Reported IPs

209.175.198.64 144.190.134.55 100.210.207.125 210.109.113.11
233.180.57.217 233.195.113.128 236.250.115.175 227.57.97.111
20.197.103.161 21.84.196.81 168.176.201.138 15.68.32.126
33.146.248.244 174.5.99.158 118.137.135.68 152.145.31.7
59.193.25.44 223.211.34.195 82.209.35.213 139.246.195.136