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: Japan

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

;; QUESTION SECTION:
;157.67.14.42.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 23 01:05:50 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 42.14.67.157.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 42.14.67.157.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
161.53.114.34 attack
Feb  1 18:49:50 srv01 sshd[4299]: Did not receive identification string from 161.53.114.34 port 34334
Feb  1 18:49:57 srv01 sshd[4302]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=161.53.114.34  user=root
Feb  1 18:49:59 srv01 sshd[4302]: Failed password for root from 161.53.114.34 port 53666 ssh2
Feb  1 18:50:31 srv01 sshd[4362]: Invalid user oracle from 161.53.114.34 port 45700
...
2020-02-02 01:55:02
123.11.199.132 attackbotsspam
Unauthorized connection attempt detected from IP address 123.11.199.132 to port 23 [J]
2020-02-02 02:02:33
118.163.186.176 attackbotsspam
Unauthorised access (Feb  1) SRC=118.163.186.176 LEN=40 TTL=235 ID=30659 TCP DPT=1433 WINDOW=1024 SYN
2020-02-02 02:03:06
144.34.248.219 attack
Unauthorized connection attempt detected from IP address 144.34.248.219 to port 2220 [J]
2020-02-02 02:09:06
145.239.87.109 attackbots
...
2020-02-02 01:27:07
122.155.11.89 attackspambots
Unauthorized connection attempt detected from IP address 122.155.11.89 to port 2220 [J]
2020-02-02 01:49:22
198.143.182.199 attackspam
22/tcp
[2020-02-01]1pkt
2020-02-02 02:05:27
192.241.232.227 attack
TCP 3389 (RDP)
2020-02-02 01:41:50
83.246.143.12 attackbots
Honeypot attack, port: 81, PTR: ip-83-246-143-12.intelbi.ru.
2020-02-02 02:08:25
145.239.89.243 attackbotsspam
Unauthorized connection attempt detected from IP address 145.239.89.243 to port 2220 [J]
2020-02-02 01:25:00
202.62.226.26 attackspam
1433/tcp
[2020-02-01]1pkt
2020-02-02 01:24:11
45.134.179.57 attackspambots
Feb  1 18:25:38 debian-2gb-nbg1-2 kernel: \[2837194.403339\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=45.134.179.57 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=31232 PROTO=TCP SPT=59849 DPT=203 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-02 01:40:57
197.51.3.189 attackbotsspam
Honeypot attack, port: 445, PTR: host-197.51.3.189.tedata.net.
2020-02-02 02:08:41
177.37.164.63 attack
Honeypot attack, port: 445, PTR: 177-37-164-63-tmp.static.brisanet.net.br.
2020-02-02 01:21:56
144.48.110.182 attack
...
2020-02-02 02:05:57

Recently Reported IPs

61.47.111.15 173.64.100.232 32.153.214.155 68.222.23.6
138.81.63.2 66.97.177.219 212.86.211.125 16.228.130.162
228.254.208.108 143.5.112.46 249.0.81.46 196.81.175.80
55.120.73.56 215.229.147.226 197.93.155.29 106.34.74.132
54.178.223.191 143.56.8.101 26.23.148.146 32.149.169.169