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

;; QUESTION SECTION:
;104.20.69.45.			IN	A

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

;; Query time: 55 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 19:59:35 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 45.69.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 45.69.20.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
157.230.129.73 attackspam
Dec 26 16:01:28 thevastnessof sshd[13671]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.129.73
...
2019-12-27 02:20:39
129.204.75.61 attackspambots
$f2bV_matches
2019-12-27 02:16:02
23.99.176.168 attack
2019-12-26T15:30:30.075077abusebot-7.cloudsearch.cf sshd[9490]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.99.176.168  user=daemon
2019-12-26T15:30:31.914000abusebot-7.cloudsearch.cf sshd[9490]: Failed password for daemon from 23.99.176.168 port 3840 ssh2
2019-12-26T15:32:32.367537abusebot-7.cloudsearch.cf sshd[9495]: Invalid user yumikof from 23.99.176.168 port 3840
2019-12-26T15:32:32.371022abusebot-7.cloudsearch.cf sshd[9495]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.99.176.168
2019-12-26T15:32:32.367537abusebot-7.cloudsearch.cf sshd[9495]: Invalid user yumikof from 23.99.176.168 port 3840
2019-12-26T15:32:34.626206abusebot-7.cloudsearch.cf sshd[9495]: Failed password for invalid user yumikof from 23.99.176.168 port 3840 ssh2
2019-12-26T15:34:47.163621abusebot-7.cloudsearch.cf sshd[9589]: Invalid user tty from 23.99.176.168 port 3840
...
2019-12-27 02:16:15
51.68.189.69 attackbots
Automatic report - Banned IP Access
2019-12-27 02:40:11
34.80.244.134 attackspambots
Dec 23 23:46:44 Aberdeen-m4-Access auth.info sshd[12513]: Invalid user vcsa from 34.80.244.134 port 49654
Dec 23 23:46:44 Aberdeen-m4-Access auth.info sshd[12513]: Failed password for invalid user vcsa from 34.80.244.134 port 49654 ssh2
Dec 23 23:46:44 Aberdeen-m4-Access auth.info sshd[12513]: Received disconnect from 34.80.244.134 port 49654:11: Bye Bye [preauth]
Dec 23 23:46:44 Aberdeen-m4-Access auth.info sshd[12513]: Disconnected from 34.80.244.134 port 49654 [preauth]
Dec 23 23:46:44 Aberdeen-m4-Access auth.notice sshguard[17606]: Attack from "34.80.244.134" on service 100 whostnameh danger 10.
Dec 23 23:46:44 Aberdeen-m4-Access auth.notice sshguard[17606]: Attack from "34.80.244.134" on service 100 whostnameh danger 10.
Dec 23 23:46:44 Aberdeen-m4-Access auth.notice sshguard[17606]: Attack from "34.80.244.134" on service 100 whostnameh danger 10.
Dec 23 23:46:44 Aberdeen-m4-Access auth.warn sshguard[17606]: Blocking "34.80.244.134/32" forever (3 attacks in 0 secs, ........
------------------------------
2019-12-27 02:29:25
120.133.132.65 attackspambots
$f2bV_matches
2019-12-27 02:24:28
118.89.61.51 attack
Dec 26 11:51:27 vps46666688 sshd[23345]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.89.61.51
Dec 26 11:51:29 vps46666688 sshd[23345]: Failed password for invalid user Password123456789 from 118.89.61.51 port 36754 ssh2
...
2019-12-27 02:48:33
111.230.246.199 attackbots
$f2bV_matches
2019-12-27 02:39:42
72.18.217.226 attack
$f2bV_matches
2019-12-27 02:47:03
95.213.176.146 attackbots
$f2bV_matches
2019-12-27 02:44:30
145.239.95.83 attackspambots
2019-12-26T17:22:54.742538abusebot-2.cloudsearch.cf sshd[18173]: Invalid user http from 145.239.95.83 port 59960
2019-12-26T17:22:54.748462abusebot-2.cloudsearch.cf sshd[18173]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.ip-145-239-95.eu
2019-12-26T17:22:54.742538abusebot-2.cloudsearch.cf sshd[18173]: Invalid user http from 145.239.95.83 port 59960
2019-12-26T17:22:56.460967abusebot-2.cloudsearch.cf sshd[18173]: Failed password for invalid user http from 145.239.95.83 port 59960 ssh2
2019-12-26T17:24:49.886987abusebot-2.cloudsearch.cf sshd[18177]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.ip-145-239-95.eu  user=root
2019-12-26T17:24:52.018293abusebot-2.cloudsearch.cf sshd[18177]: Failed password for root from 145.239.95.83 port 52366 ssh2
2019-12-26T17:26:50.066706abusebot-2.cloudsearch.cf sshd[18181]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=8
...
2019-12-27 02:32:54
129.211.68.222 attackbots
$f2bV_matches
2019-12-27 02:12:59
137.74.119.50 attackbotsspam
$f2bV_matches
2019-12-27 02:17:44
50.227.195.3 attackspam
Dec 26 17:16:29 sd-53420 sshd\[6043\]: User root from 50.227.195.3 not allowed because none of user's groups are listed in AllowGroups
Dec 26 17:16:29 sd-53420 sshd\[6043\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=50.227.195.3  user=root
Dec 26 17:16:32 sd-53420 sshd\[6043\]: Failed password for invalid user root from 50.227.195.3 port 49770 ssh2
Dec 26 17:19:02 sd-53420 sshd\[6957\]: Invalid user bekah from 50.227.195.3
Dec 26 17:19:02 sd-53420 sshd\[6957\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=50.227.195.3
...
2019-12-27 02:45:15
128.199.35.47 attack
$f2bV_matches
2019-12-27 02:16:56

Recently Reported IPs

104.20.69.14 197.23.115.27 104.20.69.70 108.167.165.166
108.167.168.29 108.167.168.74 108.167.165.66 108.167.168.47
108.167.164.60 108.167.165.59 108.167.168.34 108.167.165.34
108.167.169.119 108.167.165.131 108.167.168.38 108.167.169.186
108.167.172.112 108.167.169.44 108.167.172.131 108.167.172.12