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

Internet Service Provider: AT&T

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

;; QUESTION SECTION:
;66.122.149.116.			IN	A

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

;; Query time: 61 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 27 14:05:47 CST 2025
;; MSG SIZE  rcvd: 107
Host info
116.149.122.66.in-addr.arpa domain name pointer adsl-66-122-149-116.dsl.lsan03.pacbell.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
116.149.122.66.in-addr.arpa	name = adsl-66-122-149-116.dsl.lsan03.pacbell.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
151.80.83.249 attack
bruteforce detected
2020-05-28 15:52:45
36.111.146.209 attackbots
Invalid user admin from 36.111.146.209 port 55166
2020-05-28 15:59:28
128.199.149.164 attackbotsspam
SSH/22 MH Probe, BF, Hack -
2020-05-28 15:40:42
159.203.27.98 attackbots
Invalid user fms from 159.203.27.98 port 57372
2020-05-28 16:03:39
113.133.176.204 attackspambots
May 28 16:32:57 web1 sshd[12134]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.133.176.204  user=root
May 28 16:32:59 web1 sshd[12134]: Failed password for root from 113.133.176.204 port 33728 ssh2
May 28 16:54:26 web1 sshd[17450]: Invalid user robert from 113.133.176.204 port 51796
May 28 16:54:26 web1 sshd[17450]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.133.176.204
May 28 16:54:26 web1 sshd[17450]: Invalid user robert from 113.133.176.204 port 51796
May 28 16:54:28 web1 sshd[17450]: Failed password for invalid user robert from 113.133.176.204 port 51796 ssh2
May 28 16:59:06 web1 sshd[18598]: Invalid user anton from 113.133.176.204 port 46562
May 28 16:59:06 web1 sshd[18598]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.133.176.204
May 28 16:59:06 web1 sshd[18598]: Invalid user anton from 113.133.176.204 port 46562
May 28 16:59:08 web1 sshd[
...
2020-05-28 15:42:38
120.70.103.27 attackbotsspam
Invalid user bachner from 120.70.103.27 port 35253
2020-05-28 15:53:10
180.101.147.147 attackspambots
v+ssh-bruteforce
2020-05-28 16:01:39
190.98.210.210 attack
ssh brute force
2020-05-28 15:53:52
213.230.75.160 attack
IP 213.230.75.160 attacked honeypot on port: 8080 at 5/28/2020 4:55:11 AM
2020-05-28 15:50:46
139.199.45.83 attack
SSH login attempts.
2020-05-28 15:48:15
178.32.31.37 attackspam
Automatic report - XMLRPC Attack
2020-05-28 16:10:44
180.76.121.28 attackspambots
$f2bV_matches | Triggered by Fail2Ban at Vostok web server
2020-05-28 15:51:20
89.187.177.136 attackbotsspam
0,81-02/02 [bc01/m60] PostRequest-Spammer scoring: madrid
2020-05-28 15:34:48
88.157.229.59 attackspambots
SSH login attempts.
2020-05-28 16:03:56
222.186.175.154 attackbots
May 28 09:58:15 prod4 sshd\[7629\]: Failed password for root from 222.186.175.154 port 19220 ssh2
May 28 09:58:19 prod4 sshd\[7629\]: Failed password for root from 222.186.175.154 port 19220 ssh2
May 28 09:58:22 prod4 sshd\[7629\]: Failed password for root from 222.186.175.154 port 19220 ssh2
...
2020-05-28 16:00:24

Recently Reported IPs

170.133.114.209 238.152.22.24 168.180.100.128 196.172.21.242
20.230.176.168 165.191.5.253 40.128.85.232 93.200.43.83
123.229.108.97 217.127.4.219 94.53.10.100 14.64.84.124
214.122.196.196 8.1.55.102 37.89.161.187 234.147.149.89
225.202.77.43 8.245.75.3 216.131.157.124 128.227.237.23