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

;; QUESTION SECTION:
;48.180.165.66.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 21 04:18:00 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 66.165.180.48.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 66.165.180.48.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
185.90.116.42 attack
10/13/2019-16:19:38.735199 185.90.116.42 Protocol: 6 ET SCAN Potential SSH Scan
2019-10-14 04:24:49
168.255.251.126 attack
Feb 10 03:28:35 dillonfme sshd\[15426\]: Invalid user mb from 168.255.251.126 port 49392
Feb 10 03:28:35 dillonfme sshd\[15426\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.255.251.126
Feb 10 03:28:37 dillonfme sshd\[15426\]: Failed password for invalid user mb from 168.255.251.126 port 49392 ssh2
Feb 10 03:33:56 dillonfme sshd\[15589\]: Invalid user ftpuser from 168.255.251.126 port 40298
Feb 10 03:33:56 dillonfme sshd\[15589\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.255.251.126
...
2019-10-14 04:32:53
148.70.1.210 attack
Feb 26 10:16:03 dillonfme sshd\[32745\]: Invalid user je from 148.70.1.210 port 56694
Feb 26 10:16:03 dillonfme sshd\[32745\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.1.210
Feb 26 10:16:05 dillonfme sshd\[32745\]: Failed password for invalid user je from 148.70.1.210 port 56694 ssh2
Feb 26 10:23:06 dillonfme sshd\[394\]: Invalid user mr from 148.70.1.210 port 54350
Feb 26 10:23:06 dillonfme sshd\[394\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.1.210
...
2019-10-14 04:16:21
222.232.29.235 attack
Oct 13 16:57:24 sso sshd[29939]: Failed password for root from 222.232.29.235 port 43492 ssh2
...
2019-10-14 03:57:37
181.198.35.108 attackspam
Tried sshing with brute force.
2019-10-14 03:58:01
159.89.148.68 attack
Automatic report - Banned IP Access
2019-10-14 04:28:33
220.178.210.5 attack
Port 1433 Scan
2019-10-14 03:56:12
218.92.0.191 attackbotsspam
Oct 13 21:50:51 dcd-gentoo sshd[9454]: User root from 218.92.0.191 not allowed because none of user's groups are listed in AllowGroups
Oct 13 21:50:54 dcd-gentoo sshd[9454]: error: PAM: Authentication failure for illegal user root from 218.92.0.191
Oct 13 21:50:51 dcd-gentoo sshd[9454]: User root from 218.92.0.191 not allowed because none of user's groups are listed in AllowGroups
Oct 13 21:50:54 dcd-gentoo sshd[9454]: error: PAM: Authentication failure for illegal user root from 218.92.0.191
Oct 13 21:50:51 dcd-gentoo sshd[9454]: User root from 218.92.0.191 not allowed because none of user's groups are listed in AllowGroups
Oct 13 21:50:54 dcd-gentoo sshd[9454]: error: PAM: Authentication failure for illegal user root from 218.92.0.191
Oct 13 21:50:54 dcd-gentoo sshd[9454]: Failed keyboard-interactive/pam for invalid user root from 218.92.0.191 port 55798 ssh2
...
2019-10-14 04:00:22
159.203.36.154 attackspambots
Unauthorized SSH login attempts
2019-10-14 04:04:27
222.186.180.8 attack
Oct 13 16:22:00 ny01 sshd[2588]: Failed password for root from 222.186.180.8 port 10682 ssh2
Oct 13 16:22:12 ny01 sshd[2588]: Failed password for root from 222.186.180.8 port 10682 ssh2
Oct 13 16:22:16 ny01 sshd[2588]: Failed password for root from 222.186.180.8 port 10682 ssh2
Oct 13 16:22:16 ny01 sshd[2588]: error: maximum authentication attempts exceeded for root from 222.186.180.8 port 10682 ssh2 [preauth]
2019-10-14 04:35:49
129.213.179.77 attackbots
Oct 14 01:46:49 areeb-Workstation sshd[5209]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.179.77
Oct 14 01:46:51 areeb-Workstation sshd[5209]: Failed password for invalid user Centrum@123 from 129.213.179.77 port 15842 ssh2
...
2019-10-14 04:21:54
41.169.7.177 attackbotsspam
Oct 13 14:45:50 hcbbdb sshd\[29587\]: Invalid user Hot@123 from 41.169.7.177
Oct 13 14:45:50 hcbbdb sshd\[29587\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.169.7.177
Oct 13 14:45:52 hcbbdb sshd\[29587\]: Failed password for invalid user Hot@123 from 41.169.7.177 port 44188 ssh2
Oct 13 14:50:42 hcbbdb sshd\[30112\]: Invalid user Exploit2017 from 41.169.7.177
Oct 13 14:50:42 hcbbdb sshd\[30112\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.169.7.177
2019-10-14 04:06:43
185.90.118.18 attack
10/13/2019-16:26:45.998342 185.90.118.18 Protocol: 6 ET SCAN Potential SSH Scan
2019-10-14 04:32:39
91.74.234.154 attackspambots
Brute force SMTP login attempted.
...
2019-10-14 04:29:21
168.62.63.55 attackspam
Mar 17 01:45:39 yesfletchmain sshd\[8507\]: Invalid user pma from 168.62.63.55 port 33258
Mar 17 01:45:39 yesfletchmain sshd\[8507\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.62.63.55
Mar 17 01:45:41 yesfletchmain sshd\[8507\]: Failed password for invalid user pma from 168.62.63.55 port 33258 ssh2
Mar 17 01:51:27 yesfletchmain sshd\[8836\]: Invalid user web2 from 168.62.63.55 port 60556
Mar 17 01:51:27 yesfletchmain sshd\[8836\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.62.63.55
...
2019-10-14 04:26:52

Recently Reported IPs

74.212.151.125 225.115.174.108 64.185.132.112 150.249.71.33
96.60.119.112 255.133.52.222 52.86.33.32 173.216.29.15
204.253.17.229 118.103.64.28 226.253.184.145 80.27.131.22
151.73.125.233 186.65.241.149 119.32.46.49 174.200.224.24
199.245.40.120 221.128.195.134 215.225.175.17 217.100.184.45