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

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

;; QUESTION SECTION:
;182.142.99.20.			IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 15:39:39 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 20.99.142.182.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 20.99.142.182.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
79.241.208.125 attack
Unauthorized connection attempt detected from IP address 79.241.208.125 to port 23 [J]
2020-02-05 08:42:02
124.156.50.241 attackbots
Unauthorized connection attempt detected from IP address 124.156.50.241 to port 8118 [J]
2020-02-05 09:13:12
106.12.93.114 attack
Feb  4 22:34:57 srv01 sshd[22009]: Invalid user riehle from 106.12.93.114 port 59646
Feb  4 22:34:57 srv01 sshd[22009]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.93.114
Feb  4 22:34:57 srv01 sshd[22009]: Invalid user riehle from 106.12.93.114 port 59646
Feb  4 22:34:59 srv01 sshd[22009]: Failed password for invalid user riehle from 106.12.93.114 port 59646 ssh2
Feb  4 22:37:25 srv01 sshd[22251]: Invalid user downloads from 106.12.93.114 port 54000
...
2020-02-05 08:56:11
110.136.48.122 attack
Unauthorized connection attempt detected from IP address 110.136.48.122 to port 81 [J]
2020-02-05 08:55:11
220.134.199.90 attackbots
Unauthorized connection attempt detected from IP address 220.134.199.90 to port 4567 [J]
2020-02-05 08:45:55
121.159.114.29 attackspam
Unauthorized connection attempt detected from IP address 121.159.114.29 to port 2220 [J]
2020-02-05 08:52:23
139.198.191.86 attackbotsspam
Unauthorized connection attempt detected from IP address 139.198.191.86 to port 2220 [J]
2020-02-05 09:12:44
175.24.107.201 attack
Unauthorized connection attempt detected from IP address 175.24.107.201 to port 2220 [J]
2020-02-05 08:48:49
219.77.180.214 attackbots
Unauthorized connection attempt detected from IP address 219.77.180.214 to port 5555 [J]
2020-02-05 09:05:18
73.24.240.230 attack
Unauthorized connection attempt detected from IP address 73.24.240.230 to port 80 [J]
2020-02-05 08:42:24
93.171.33.234 attackbots
Unauthorized connection attempt detected from IP address 93.171.33.234 to port 81 [J]
2020-02-05 08:40:18
203.170.134.152 attackbotsspam
Unauthorized connection attempt detected from IP address 203.170.134.152 to port 80 [J]
2020-02-05 08:47:25
46.161.27.218 attackspam
Unauthorized connection attempt detected from IP address 46.161.27.218 to port 5900
2020-02-05 09:00:38
189.173.30.187 attackspambots
Unauthorized connection attempt detected from IP address 189.173.30.187 to port 2323 [J]
2020-02-05 09:09:14
103.78.81.227 attack
Unauthorized connection attempt detected from IP address 103.78.81.227 to port 2220 [J]
2020-02-05 08:57:15

Recently Reported IPs

182.141.183.241 182.142.130.55 182.139.87.216 182.145.92.79
182.140.5.6 182.146.107.253 182.143.69.204 182.146.237.124
182.139.200.238 182.148.107.78 182.148.124.127 182.148.156.52
182.149.121.5 182.149.162.141 182.149.116.230 182.148.156.82
182.149.94.147 182.149.66.65 182.150.187.37 182.150.171.88