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

;; QUESTION SECTION:
;66.135.48.42.			IN	A

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

;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 23 02:44:52 CST 2025
;; MSG SIZE  rcvd: 105
Host info
42.48.135.66.in-addr.arpa domain name pointer server1.hmbsystems.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
42.48.135.66.in-addr.arpa	name = server1.hmbsystems.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
58.62.197.180 attackspam
badbot
2019-11-24 00:52:09
137.74.192.142 attack
Nov 22 06:28:07 kmh-mb-001 sshd[23970]: Invalid user bosiljka from 137.74.192.142 port 52058
Nov 22 06:28:07 kmh-mb-001 sshd[23970]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.192.142
Nov 22 06:28:10 kmh-mb-001 sshd[23970]: Failed password for invalid user bosiljka from 137.74.192.142 port 52058 ssh2
Nov 22 06:28:10 kmh-mb-001 sshd[23970]: Received disconnect from 137.74.192.142 port 52058:11: Bye Bye [preauth]
Nov 22 06:28:10 kmh-mb-001 sshd[23970]: Disconnected from 137.74.192.142 port 52058 [preauth]
Nov 22 06:48:32 kmh-mb-001 sshd[24777]: Invalid user hasenknopf from 137.74.192.142 port 34422
Nov 22 06:48:32 kmh-mb-001 sshd[24777]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.192.142
Nov 22 06:48:34 kmh-mb-001 sshd[24777]: Failed password for invalid user hasenknopf from 137.74.192.142 port 34422 ssh2
Nov 22 06:48:34 kmh-mb-001 sshd[24777]: Received disconnect from ........
-------------------------------
2019-11-24 00:15:17
123.134.253.147 attackbots
badbot
2019-11-24 00:40:51
156.212.45.66 attackspambots
19/11/23@09:26:01: FAIL: IoT-SSH address from=156.212.45.66
...
2019-11-24 00:24:49
180.68.177.15 attackbots
Nov 23 16:20:33 web8 sshd\[25582\]: Invalid user pcap from 180.68.177.15
Nov 23 16:20:33 web8 sshd\[25582\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.68.177.15
Nov 23 16:20:34 web8 sshd\[25582\]: Failed password for invalid user pcap from 180.68.177.15 port 54516 ssh2
Nov 23 16:25:12 web8 sshd\[27778\]: Invalid user jason from 180.68.177.15
Nov 23 16:25:12 web8 sshd\[27778\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.68.177.15
2019-11-24 00:33:09
89.133.62.227 attackbotsspam
Nov 23 16:40:16 MK-Soft-VM7 sshd[1789]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.133.62.227 
Nov 23 16:40:18 MK-Soft-VM7 sshd[1789]: Failed password for invalid user install from 89.133.62.227 port 39330 ssh2
...
2019-11-24 00:29:32
63.88.23.195 attackbotsspam
63.88.23.195 was recorded 5 times by 2 hosts attempting to connect to the following ports: 80. Incident counter (4h, 24h, all-time): 5, 5, 469
2019-11-24 00:18:37
185.156.73.3 attackbots
11230/tcp 11231/tcp 11232/tcp...
[2019-10-17/11-23]1904pkt,589pt.(tcp)
2019-11-24 00:09:24
148.70.101.245 attackbotsspam
Nov 23 05:15:31 auw2 sshd\[25062\]: Invalid user sainte from 148.70.101.245
Nov 23 05:15:31 auw2 sshd\[25062\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.101.245
Nov 23 05:15:32 auw2 sshd\[25062\]: Failed password for invalid user sainte from 148.70.101.245 port 42730 ssh2
Nov 23 05:21:40 auw2 sshd\[25584\]: Invalid user mastaler from 148.70.101.245
Nov 23 05:21:40 auw2 sshd\[25584\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.101.245
2019-11-24 00:22:18
92.118.160.33 attackspambots
92.118.160.33 was recorded 5 times by 4 hosts attempting to connect to the following ports: 1026,16010,593,401,554. Incident counter (4h, 24h, all-time): 5, 8, 254
2019-11-24 00:42:07
223.74.230.145 attack
badbot
2019-11-24 00:31:49
115.231.220.133 attack
ET SCAN Suspicious inbound to mySQL port 3306 - port: 3306 proto: TCP cat: Potentially Bad Traffic
2019-11-24 00:35:54
111.231.66.135 attackbotsspam
Nov 23 17:41:40 legacy sshd[10435]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.66.135
Nov 23 17:41:42 legacy sshd[10435]: Failed password for invalid user qunlian789 from 111.231.66.135 port 60588 ssh2
Nov 23 17:46:29 legacy sshd[10601]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.66.135
...
2019-11-24 00:47:58
118.24.57.240 attackbots
Nov 23 11:41:07 woltan sshd[29618]: Failed password for invalid user quentas from 118.24.57.240 port 58682 ssh2
2019-11-24 00:27:23
157.55.39.193 attackspambots
Automatic report - Banned IP Access
2019-11-24 00:14:56

Recently Reported IPs

217.231.34.55 46.30.237.49 9.15.186.101 234.223.116.20
153.61.43.147 107.241.114.44 9.240.82.211 134.42.224.126
93.122.64.66 223.102.104.66 127.58.230.156 206.213.125.190
255.224.171.47 194.139.111.72 174.141.98.43 41.138.230.165
54.189.100.215 213.85.175.135 174.196.189.114 3.128.152.179