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

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

;; QUESTION SECTION:
;104.20.6.201.			IN	A

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

;; Query time: 75 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 15:44:38 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 201.6.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 201.6.20.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
45.80.39.228 attackbots
v+ssh-bruteforce
2019-06-24 13:54:55
142.93.221.103 attackspambots
Invalid user admin from 142.93.221.103 port 52712
2019-06-24 13:40:10
107.172.3.124 attackspam
Invalid user nagios from 107.172.3.124 port 52060
2019-06-24 13:09:31
174.83.76.187 attackbots
[SPAM] could you meet me today?
2019-06-24 12:58:34
104.211.60.207 attack
Fail2Ban Ban Triggered
2019-06-24 13:45:33
177.155.94.7 attack
Invalid user admin from 177.155.94.7 port 58375
2019-06-24 13:14:22
181.223.213.28 attack
Invalid user postgres from 181.223.213.28 port 56956
2019-06-24 13:37:00
217.182.204.107 attack
Invalid user timson from 217.182.204.107 port 43660
2019-06-24 13:56:33
139.59.92.10 attack
Invalid user server from 139.59.92.10 port 54150
2019-06-24 13:40:47
202.105.18.222 attack
Invalid user xx from 202.105.18.222 port 12835
2019-06-24 13:12:12
165.22.41.73 attackspam
Jun 24 01:14:23 XXX sshd[28934]: User r.r from 165.22.41.73 not allowed because none of user's groups are listed in AllowGroups
Jun 24 01:14:23 XXX sshd[28934]: Received disconnect from 165.22.41.73: 11: Bye Bye [preauth]
Jun 24 01:14:24 XXX sshd[28936]: Invalid user admin from 165.22.41.73
Jun 24 01:14:24 XXX sshd[28936]: Received disconnect from 165.22.41.73: 11: Bye Bye [preauth]
Jun 24 01:14:25 XXX sshd[28938]: Invalid user admin from 165.22.41.73
Jun 24 01:14:25 XXX sshd[28938]: Received disconnect from 165.22.41.73: 11: Bye Bye [preauth]
Jun 24 01:14:26 XXX sshd[28940]: Invalid user user from 165.22.41.73
Jun 24 01:14:26 XXX sshd[28940]: Received disconnect from 165.22.41.73: 11: Bye Bye [preauth]
Jun 24 01:14:26 XXX sshd[28942]: Invalid user ubnt from 165.22.41.73
Jun 24 01:14:26 XXX sshd[28942]: Received disconnect from 165.22.41.73: 11: Bye Bye [preauth]
Jun 24 01:14:27 XXX sshd[28944]: Invalid user admin from 165.22.41.73
Jun 24 01:14:27 XXX sshd[28944]: Recei........
-------------------------------
2019-06-24 13:15:49
109.130.134.98 attackbotsspam
Invalid user hduser from 109.130.134.98 port 56916
2019-06-24 13:43:42
68.183.80.232 attackspambots
Invalid user admin from 68.183.80.232 port 44180
2019-06-24 13:52:34
172.16.9.36 attack
[SPAM] You have a new message from Pak'nSave
2019-06-24 12:59:49
95.69.137.131 attackbotsspam
Invalid user test from 95.69.137.131 port 59694
2019-06-24 13:24:25

Recently Reported IPs

104.20.5.74 104.20.6.232 104.20.79.214 104.20.86.128
104.20.83.250 104.20.88.128 104.20.87.128 104.20.80.214
104.20.98.67 104.200.151.141 104.200.135.156 104.200.110.242
104.20.85.128 104.20.84.250 104.200.151.83 165.174.59.217
104.200.26.66 104.202.173.83 104.206.33.170 104.207.144.77