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: Brockport

Region: New York

Country: United States

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

;; QUESTION SECTION:
;137.21.172.30.			IN	A

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

;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 13 23:00:24 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 30.172.21.137.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 30.172.21.137.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
217.218.21.242 attackbots
Jan 29 01:45:11 server sshd\[30606\]: Invalid user dheeman from 217.218.21.242
Jan 29 01:45:12 server sshd\[30606\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.218.21.242 
Jan 29 01:45:13 server sshd\[30606\]: Failed password for invalid user dheeman from 217.218.21.242 port 24126 ssh2
Jan 29 01:49:22 server sshd\[30939\]: Invalid user rusangu from 217.218.21.242
Jan 29 01:49:22 server sshd\[30939\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.218.21.242 
...
2020-01-29 06:56:59
111.224.234.16 attackspam
Unauthorized connection attempt detected from IP address 111.224.234.16 to port 8080 [J]
2020-01-29 07:05:30
45.83.67.192 attackspambots
Unauthorized connection attempt detected from IP address 45.83.67.192 to port 21 [J]
2020-01-29 06:53:08
114.35.156.220 attackspambots
Unauthorized connection attempt detected from IP address 114.35.156.220 to port 23 [J]
2020-01-29 06:42:44
43.224.9.113 attackbotsspam
Unauthorized connection attempt detected from IP address 43.224.9.113 to port 23 [J]
2020-01-29 07:11:04
142.93.140.242 attack
Unauthorized connection attempt detected from IP address 142.93.140.242 to port 2220 [J]
2020-01-29 06:39:24
62.30.199.229 attackbots
Unauthorized connection attempt detected from IP address 62.30.199.229 to port 23 [J]
2020-01-29 06:49:43
180.177.105.38 attackspam
Unauthorized connection attempt detected from IP address 180.177.105.38 to port 4567 [J]
2020-01-29 07:01:17
36.71.239.114 attack
Unauthorized connection attempt detected from IP address 36.71.239.114 to port 80 [J]
2020-01-29 07:11:34
170.106.81.36 attackspambots
Unauthorized connection attempt detected from IP address 170.106.81.36 to port 1471 [J]
2020-01-29 06:37:14
190.43.92.88 attackbotsspam
Unauthorized connection attempt detected from IP address 190.43.92.88 to port 80 [J]
2020-01-29 06:59:41
109.97.26.73 attack
Unauthorized connection attempt detected from IP address 109.97.26.73 to port 4567 [J]
2020-01-29 07:06:01
31.25.134.178 attackspam
Unauthorized connection attempt detected from IP address 31.25.134.178 to port 81 [J]
2020-01-29 06:54:06
54.36.163.188 attack
Unauthorized connection attempt detected from IP address 54.36.163.188 to port 2220 [J]
2020-01-29 07:09:49
45.83.67.196 attackbots
Unauthorized connection attempt detected from IP address 45.83.67.196 to port 21 [J]
2020-01-29 06:52:40

Recently Reported IPs

7.211.154.246 213.167.193.219 139.84.96.120 54.146.50.39
66.214.225.145 218.9.68.229 242.70.39.239 233.130.107.119
208.168.189.199 252.13.47.77 205.189.165.61 241.157.51.241
3.230.198.21 181.62.195.88 187.83.117.75 46.211.165.199
188.42.253.34 4.156.96.253 160.211.196.247 75.129.238.170