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:
IP Type Details Datetime
104.20.212.42 spambots
Vr network
2023-03-18 06:45:21
104.20.2.253 attackbotsspam
TCP Port Scanning
2020-03-12 04:40:15
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.20.2.129
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51758
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.20.2.129.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 02:03:51 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 129.2.20.104.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 129.2.20.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
62.4.13.108 attack
Jun 25 02:54:09 MainVPS sshd[7873]: Invalid user cms from 62.4.13.108 port 52058
Jun 25 02:54:09 MainVPS sshd[7873]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.4.13.108
Jun 25 02:54:09 MainVPS sshd[7873]: Invalid user cms from 62.4.13.108 port 52058
Jun 25 02:54:11 MainVPS sshd[7873]: Failed password for invalid user cms from 62.4.13.108 port 52058 ssh2
Jun 25 02:56:36 MainVPS sshd[8075]: Invalid user mashby from 62.4.13.108 port 51188
...
2019-06-25 11:38:46
181.15.154.154 attackbots
Autoban   181.15.154.154 AUTH/CONNECT
2019-06-25 11:41:38
181.166.106.224 attackbots
Autoban   181.166.106.224 AUTH/CONNECT
2019-06-25 11:39:58
179.43.160.47 attackbots
Autoban   179.43.160.47 AUTH/CONNECT
2019-06-25 12:05:21
179.6.212.62 attackspam
Autoban   179.6.212.62 AUTH/CONNECT
2019-06-25 12:03:06
180.155.79.139 attackspam
Autoban   180.155.79.139 AUTH/CONNECT
2019-06-25 11:56:15
179.4.133.218 attackspam
Autoban   179.4.133.218 AUTH/CONNECT
2019-06-25 12:08:35
180.240.201.1 attack
Autoban   180.240.201.1 AUTH/CONNECT
2019-06-25 11:50:30
190.217.26.154 attack
$f2bV_matches
2019-06-25 11:28:57
180.177.98.42 attackspambots
Autoban   180.177.98.42 AUTH/CONNECT
2019-06-25 11:55:45
174.105.201.174 attackbots
2019-06-24T17:59:53.641179WS-Zach sshd[31580]: Invalid user lada from 174.105.201.174 port 47308
2019-06-24T17:59:53.644876WS-Zach sshd[31580]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.105.201.174
2019-06-24T17:59:53.641179WS-Zach sshd[31580]: Invalid user lada from 174.105.201.174 port 47308
2019-06-24T17:59:56.003150WS-Zach sshd[31580]: Failed password for invalid user lada from 174.105.201.174 port 47308 ssh2
2019-06-24T18:02:05.647924WS-Zach sshd[455]: Invalid user mcadmin from 174.105.201.174 port 43308
...
2019-06-25 11:40:55
189.235.82.124 attackspambots
firewall-block, port(s): 8080/tcp
2019-06-25 12:09:28
181.166.207.74 attack
Autoban   181.166.207.74 AUTH/CONNECT
2019-06-25 11:39:22
87.228.67.124 attackbots
Jun 25 00:01:59 xeon sshd[12494]: Invalid user zimbra from 87.228.67.124
2019-06-25 11:54:41
179.38.5.171 attackbotsspam
Autoban   179.38.5.171 AUTH/CONNECT
2019-06-25 12:08:04

Recently Reported IPs

104.21.66.30 104.20.198.82 104.20.2.153 104.20.199.129
104.20.2.117 104.20.2.248 104.20.199.82 104.20.2.118
104.20.2.64 104.20.20.178 104.20.2.79 104.20.20.236
104.21.66.32 104.20.20.237 130.117.10.182 104.20.20.251
104.20.20.39 104.20.20.74 104.20.20.56 104.20.200.67