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

;; QUESTION SECTION:
;104.20.9.69.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 19:27:57 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 69.9.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 69.9.20.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
142.93.58.123 attackbotsspam
Jul  6 11:51:20 server sshd\[2190\]: Invalid user frontdesk from 142.93.58.123
Jul  6 11:51:20 server sshd\[2190\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.58.123
Jul  6 11:51:22 server sshd\[2190\]: Failed password for invalid user frontdesk from 142.93.58.123 port 33636 ssh2
...
2019-07-12 04:38:27
142.93.198.152 attack
May 24 15:16:51 server sshd\[177642\]: Invalid user merje from 142.93.198.152
May 24 15:16:51 server sshd\[177642\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.198.152
May 24 15:16:53 server sshd\[177642\]: Failed password for invalid user merje from 142.93.198.152 port 54392 ssh2
...
2019-07-12 05:02:35
142.93.212.101 attackbots
Apr 18 13:11:22 server sshd\[150468\]: Invalid user test from 142.93.212.101
Apr 18 13:11:22 server sshd\[150468\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.212.101
Apr 18 13:11:24 server sshd\[150468\]: Failed password for invalid user test from 142.93.212.101 port 50634 ssh2
...
2019-07-12 04:56:28
142.93.237.233 attackbotsspam
Jul  3 06:10:52 server sshd\[22469\]: Invalid user globe from 142.93.237.233
Jul  3 06:10:52 server sshd\[22469\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.237.233
Jul  3 06:10:54 server sshd\[22469\]: Failed password for invalid user globe from 142.93.237.233 port 51934 ssh2
...
2019-07-12 04:51:33
142.93.216.172 attack
Apr 17 14:59:56 server sshd\[110238\]: Invalid user ftp_test from 142.93.216.172
Apr 17 14:59:56 server sshd\[110238\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.216.172
Apr 17 14:59:58 server sshd\[110238\]: Failed password for invalid user ftp_test from 142.93.216.172 port 35738 ssh2
...
2019-07-12 04:55:33
144.21.80.96 attackbotsspam
Jun  4 12:03:23 server sshd\[132375\]: Invalid user school from 144.21.80.96
Jun  4 12:03:23 server sshd\[132375\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.21.80.96
Jun  4 12:03:25 server sshd\[132375\]: Failed password for invalid user school from 144.21.80.96 port 37097 ssh2
...
2019-07-12 04:24:33
103.118.113.14 attackspambots
Jul 11 16:01:10 rigel postfix/smtpd[18540]: connect from unknown[103.118.113.14]
Jul 11 16:01:12 rigel postfix/smtpd[18540]: warning: unknown[103.118.113.14]: SASL CRAM-MD5 authentication failed: authentication failure
Jul 11 16:01:12 rigel postfix/smtpd[18540]: warning: unknown[103.118.113.14]: SASL PLAIN authentication failed: authentication failure
Jul 11 16:01:13 rigel postfix/smtpd[18540]: warning: unknown[103.118.113.14]: SASL LOGIN authentication failed: authentication failure


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=103.118.113.14
2019-07-12 04:32:21
104.152.52.23 attackspam
A portscan was detected. Details about the event:

Time.............: 2019-07-11 09:46:07

Source IP address: 104.152.52.23 (internettl.org)
        
-- 
System Uptime      : 42 days 0 hours 16 minutes
System Load        : 0.24
System Version     : Sophos UTM 9.603-1
2019-07-12 04:20:57
59.33.140.148 attackbotsspam
Automatic report
2019-07-12 04:42:43
178.220.205.50 attackspambots
LGS,WP GET /wp-login.php
2019-07-12 04:54:38
142.93.58.151 attackbots
Jul  5 10:20:37 server sshd\[179250\]: Invalid user admin from 142.93.58.151
Jul  5 10:20:37 server sshd\[179250\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.58.151
Jul  5 10:20:39 server sshd\[179250\]: Failed password for invalid user admin from 142.93.58.151 port 44306 ssh2
...
2019-07-12 04:37:22
51.104.7.122 attackbotsspam
Apr 25 16:55:48 mail sshd\[53031\]: Invalid user hl from 51.104.7.122
Apr 25 16:55:48 mail sshd\[53031\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.104.7.122
Apr 25 16:55:50 mail sshd\[53031\]: Failed password for invalid user hl from 51.104.7.122 port 45348 ssh2
Apr 25 16:59:45 mail sshd\[53063\]: Invalid user jr from 51.104.7.122
Apr 25 16:59:45 mail sshd\[53063\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.104.7.122
Apr 25 16:59:47 mail sshd\[53063\]: Failed password for invalid user jr from 51.104.7.122 port 55006 ssh2
Apr 25 17:02:23 mail sshd\[53088\]: Invalid user odoo from 51.104.7.122
Apr 25 17:02:23 mail sshd\[53088\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.104.7.122
Apr 25 17:02:25 mail sshd\[53088\]: Failed password for invalid user odoo from 51.104.7.122 port 53202 ssh2
Apr 25 17:05:19 mail sshd\[53144\]: Invalid user uo from 51.104.7.122
2019-07-12 04:44:50
193.32.163.182 attackbotsspam
Jul 11 22:34:39 fr01 sshd[7084]: Invalid user admin from 193.32.163.182
...
2019-07-12 04:44:01
46.3.96.70 attackspam
firewall-block, port(s): 19446/tcp, 19448/tcp, 19454/tcp
2019-07-12 04:22:51
40.117.170.239 attack
Jul 11 05:33:48 mxgate1 postfix/postscreen[10360]: CONNECT from [40.117.170.239]:46787 to [176.31.12.44]:25
Jul 11 05:33:54 mxgate1 postfix/postscreen[10360]: PASS NEW [40.117.170.239]:46787
Jul 11 05:33:54 mxgate1 postfix/smtpd[10366]: connect from unknown[40.117.170.239]
Jul x@x
Jul 11 05:33:54 mxgate1 postfix/smtpd[10366]: disconnect from unknown[40.117.170.239] ehlo=1 mail=1 rcpt=0/1 data=0/1 quhostname=1 commands=3/5
Jul 11 05:43:54 mxgate1 postfix/anvil[10369]: statistics: max connection rate 1/60s for (smtpd:40.117.170.239) at Jul 11 05:33:54
Jul 11 05:43:54 mxgate1 postfix/anvil[10369]: statistics: max connection count 1 for (smtpd:40.117.170.239) at Jul 11 05:33:54
Jul 11 05:43:54 mxgate1 postfix/anvil[10369]: statistics: max message rate 1/60s for (smtpd:40.117.170.239) at Jul 11 05:33:54
Jul 11 05:43:54 mxgate1 postfix/postscreen[10544]: CONNECT from [40.117.170.239]:55261 to [176.31.12.44]:25
Jul 11 05:43:54 mxgate1 postfix/postscreen[10544]: PASS OLD [40.11........
-------------------------------
2019-07-12 04:57:54

Recently Reported IPs

104.20.90.76 104.20.9.101 104.20.91.76 104.20.91.164
104.20.91.193 104.18.183.44 104.18.183.59 104.18.184.11
104.207.253.95 104.207.242.225 104.207.253.137 104.207.244.172
104.207.248.119 104.207.242.159 104.207.254.129 104.207.251.28
104.207.246.214 104.207.254.13 104.207.253.154 104.207.239.253