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: Taiwan (Province of China)

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

;; QUESTION SECTION:
;42.66.57.2.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 22 15:22:04 CST 2025
;; MSG SIZE  rcvd: 103
Host info
2.57.66.42.in-addr.arpa domain name pointer 42-66-57-2.emome-ip.hinet.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
2.57.66.42.in-addr.arpa	name = 42-66-57-2.emome-ip.hinet.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
198.108.67.110 attackbots
23184/tcp 8037/tcp 86/tcp...
[2019-12-12/2020-02-11]101pkt,97pt.(tcp)
2020-02-12 05:44:30
5.89.64.166 attackbotsspam
Feb 11 11:40:52 firewall sshd[17287]: Invalid user ffy from 5.89.64.166
Feb 11 11:40:54 firewall sshd[17287]: Failed password for invalid user ffy from 5.89.64.166 port 59243 ssh2
Feb 11 11:47:06 firewall sshd[17591]: Invalid user hgj from 5.89.64.166
...
2020-02-12 05:34:54
212.237.131.162 attackspam
02/11/2020-20:44:38.745232 212.237.131.162 Protocol: 6 ET TOR Known Tor Relay/Router (Not Exit) Node Traffic group 336
2020-02-12 05:51:45
128.199.81.66 attackspam
Feb 11 21:06:15 debian-2gb-nbg1-2 kernel: \[3710806.926977\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=128.199.81.66 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x40 TTL=242 ID=29172 PROTO=TCP SPT=52623 DPT=12021 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-12 05:32:14
41.41.77.20 attackspambots
445/tcp 445/tcp 445/tcp
[2019-12-29/2020-02-11]3pkt
2020-02-12 05:28:01
2.37.198.220 attackspam
Unauthorized SSH login attempts
2020-02-12 05:46:18
156.222.216.52 attackbots
20/2/11@08:39:14: FAIL: Alarm-Network address from=156.222.216.52
...
2020-02-12 05:45:35
103.217.121.5 attack
" "
2020-02-12 05:50:46
213.174.22.50 attackspambots
445/tcp 445/tcp
[2020-01-17/02-11]2pkt
2020-02-12 05:25:49
152.136.37.135 attackbots
2020-02-11T16:43:09.572349  sshd[5070]: Invalid user aeu from 152.136.37.135 port 55522
2020-02-11T16:43:09.585782  sshd[5070]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.37.135
2020-02-11T16:43:09.572349  sshd[5070]: Invalid user aeu from 152.136.37.135 port 55522
2020-02-11T16:43:11.735329  sshd[5070]: Failed password for invalid user aeu from 152.136.37.135 port 55522 ssh2
2020-02-11T16:48:19.413289  sshd[5237]: Invalid user yqi from 152.136.37.135 port 56340
...
2020-02-12 05:31:47
120.132.22.92 attackbots
ssh failed login
2020-02-12 05:58:56
221.12.175.66 attack
$f2bV_matches_ltvn
2020-02-12 05:21:17
169.197.108.6 attack
web Attack on Wordpress site at 2020-02-10.
2020-02-12 05:58:27
220.248.113.26 attackbotsspam
1433/tcp 1433/tcp 1433/tcp
[2020-01-07/02-11]3pkt
2020-02-12 05:23:33
196.61.38.138 attackbotsspam
Unauthorized connection attempt from IP address 196.61.38.138 on Port 445(SMB)
2020-02-12 05:39:40

Recently Reported IPs

181.229.252.13 26.185.229.109 201.37.97.37 141.213.125.71
104.38.183.217 133.133.117.86 12.208.197.37 121.170.129.156
151.204.203.40 88.245.77.121 193.158.254.38 108.5.156.187
54.135.222.232 89.210.171.178 57.227.99.84 101.216.175.239
88.186.199.25 189.67.58.27 135.224.200.105 238.117.137.38