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: United States of America (the)

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

;; QUESTION SECTION:
;64.42.99.250.			IN	A

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

;; Query time: 34 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 19 18:45:04 CST 2025
;; MSG SIZE  rcvd: 105
Host info
250.99.42.64.in-addr.arpa domain name pointer 64-42-99-250.atgi.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
250.99.42.64.in-addr.arpa	name = 64-42-99-250.atgi.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
177.184.131.122 attackbots
(sshd) Failed SSH login from 177.184.131.122 (BR/Brazil/-): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Feb  9 01:45:55 ubnt-55d23 sshd[28485]: Did not receive identification string from 177.184.131.122 port 54647
Feb  9 01:47:05 ubnt-55d23 sshd[28492]: Invalid user support from 177.184.131.122 port 52470
2020-02-09 09:41:57
159.226.170.18 attack
Feb  5 11:32:35 mail sshd[4027]: Failed password for invalid user ukw from 159.226.170.18 port 62300 ssh2
Feb  5 11:32:35 mail sshd[4027]: Received disconnect from 159.226.170.18: 11: Bye Bye [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=159.226.170.18
2020-02-09 10:03:40
80.82.77.243 attackspam
Feb  9 02:53:34 debian-2gb-nbg1-2 kernel: \[3472452.496323\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=80.82.77.243 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=27826 PROTO=TCP SPT=56286 DPT=25538 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-09 10:02:38
139.162.11.43 attackbots
Honeypot hit.
2020-02-09 09:55:29
106.12.182.142 attackspambots
Feb  9 00:24:36 goofy sshd\[6636\]: Invalid user vrd from 106.12.182.142
Feb  9 00:24:36 goofy sshd\[6636\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.182.142
Feb  9 00:24:39 goofy sshd\[6636\]: Failed password for invalid user vrd from 106.12.182.142 port 40322 ssh2
Feb  9 00:48:30 goofy sshd\[7826\]: Invalid user iig from 106.12.182.142
Feb  9 00:48:30 goofy sshd\[7826\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.182.142
2020-02-09 09:45:48
181.65.177.126 attack
1581209219 - 02/09/2020 01:46:59 Host: 181.65.177.126/181.65.177.126 Port: 445 TCP Blocked
2020-02-09 10:06:11
200.57.111.161 attackspambots
Automatic report - Port Scan Attack
2020-02-09 09:40:38
222.186.173.226 attack
Feb  9 06:53:26 gw1 sshd[18363]: Failed password for root from 222.186.173.226 port 49181 ssh2
Feb  9 06:53:39 gw1 sshd[18363]: error: maximum authentication attempts exceeded for root from 222.186.173.226 port 49181 ssh2 [preauth]
...
2020-02-09 09:53:55
202.129.16.187 attack
firewall-block, port(s): 445/tcp
2020-02-09 10:04:41
49.88.112.62 attackspambots
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.62  user=root
Failed password for root from 49.88.112.62 port 20334 ssh2
Failed password for root from 49.88.112.62 port 20334 ssh2
Failed password for root from 49.88.112.62 port 20334 ssh2
Failed password for root from 49.88.112.62 port 20334 ssh2
2020-02-09 09:32:30
80.82.70.118 attackspam
02/09/2020-02:09:52.930651 80.82.70.118 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 82
2020-02-09 09:55:57
118.24.13.248 attackbotsspam
2020-02-08T19:12:47.1427771495-001 sshd[45216]: Invalid user qcz from 118.24.13.248 port 58740
2020-02-08T19:12:47.1458241495-001 sshd[45216]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.13.248
2020-02-08T19:12:47.1427771495-001 sshd[45216]: Invalid user qcz from 118.24.13.248 port 58740
2020-02-08T19:12:49.1426421495-001 sshd[45216]: Failed password for invalid user qcz from 118.24.13.248 port 58740 ssh2
2020-02-08T19:30:48.4451491495-001 sshd[46319]: Invalid user se from 118.24.13.248 port 33230
2020-02-08T19:30:48.4511111495-001 sshd[46319]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.13.248
2020-02-08T19:30:48.4451491495-001 sshd[46319]: Invalid user se from 118.24.13.248 port 33230
2020-02-08T19:30:50.5181191495-001 sshd[46319]: Failed password for invalid user se from 118.24.13.248 port 33230 ssh2
2020-02-08T19:33:27.5346801495-001 sshd[46428]: Invalid user xoa from 118.24.13.248
...
2020-02-09 09:45:09
35.178.16.1 attackbotsspam
WordPress login Brute force / Web App Attack on client site.
2020-02-09 09:52:10
106.12.98.14 attack
Feb  9 02:25:21 dedicated sshd[14623]: Invalid user six from 106.12.98.14 port 56288
2020-02-09 09:43:32
211.169.249.156 attackbotsspam
Feb  9 02:35:36 legacy sshd[20589]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.169.249.156
Feb  9 02:35:39 legacy sshd[20589]: Failed password for invalid user eob from 211.169.249.156 port 52184 ssh2
Feb  9 02:38:47 legacy sshd[20812]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.169.249.156
...
2020-02-09 09:49:18

Recently Reported IPs

76.178.211.5 252.198.104.134 28.234.83.196 179.189.219.16
100.31.146.235 55.228.183.200 94.192.181.196 107.81.41.87
175.162.82.41 249.137.254.179 168.125.135.162 188.192.16.54
9.130.193.68 248.206.124.11 179.163.171.1 73.209.152.8
126.0.44.38 251.151.0.161 96.69.144.99 139.79.114.200