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

;; QUESTION SECTION:
;104.21.5.13.			IN	A

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

;; Query time: 68 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 23:20:27 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 13.5.21.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 13.5.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
185.162.235.213 attackbotsspam
Mar 12 23:09:01 web9 sshd\[21912\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.162.235.213  user=root
Mar 12 23:09:03 web9 sshd\[21912\]: Failed password for root from 185.162.235.213 port 59364 ssh2
Mar 12 23:13:20 web9 sshd\[22792\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.162.235.213  user=root
Mar 12 23:13:22 web9 sshd\[22792\]: Failed password for root from 185.162.235.213 port 49050 ssh2
Mar 12 23:17:39 web9 sshd\[23458\]: Invalid user emserver from 185.162.235.213
Mar 12 23:17:39 web9 sshd\[23458\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.162.235.213
2020-03-13 18:59:05
180.167.195.167 attack
Mar 13 11:41:11 hosting180 sshd[20245]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.167.195.167  user=root
Mar 13 11:41:12 hosting180 sshd[20245]: Failed password for root from 180.167.195.167 port 52456 ssh2
...
2020-03-13 18:59:36
118.89.38.98 attack
Invalid user test from 118.89.38.98 port 43304
2020-03-13 18:23:08
122.51.49.32 attackspam
Mar 13 09:51:54 vlre-nyc-1 sshd\[2987\]: Invalid user joyoudata from 122.51.49.32
Mar 13 09:51:54 vlre-nyc-1 sshd\[2987\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.49.32
Mar 13 09:51:57 vlre-nyc-1 sshd\[2987\]: Failed password for invalid user joyoudata from 122.51.49.32 port 44072 ssh2
Mar 13 10:00:57 vlre-nyc-1 sshd\[3158\]: Invalid user user from 122.51.49.32
Mar 13 10:00:57 vlre-nyc-1 sshd\[3158\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.49.32
...
2020-03-13 18:21:38
5.182.26.22 attackspambots
20 attempts against mh-ssh on echoip
2020-03-13 18:45:52
106.13.103.1 attackspam
Mar 13 17:24:16 webhost01 sshd[31122]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.103.1
Mar 13 17:24:18 webhost01 sshd[31122]: Failed password for invalid user guest from 106.13.103.1 port 53158 ssh2
...
2020-03-13 18:52:35
183.134.217.238 attack
Mar 13 04:20:15 dallas01 sshd[28730]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.134.217.238
Mar 13 04:20:16 dallas01 sshd[28730]: Failed password for invalid user debug from 183.134.217.238 port 55226 ssh2
Mar 13 04:22:03 dallas01 sshd[29231]: Failed password for root from 183.134.217.238 port 38444 ssh2
2020-03-13 18:55:02
64.225.12.205 attackbots
2020-03-12 UTC: (31x) - appuser,dev,fctr,gerrit2,musikbot,nproc,pengcan,root(17x),uftp,user12,wp,yangx,yaoyiming,zengzhen,zope
2020-03-13 18:28:13
178.154.171.126 attackspam
[Fri Mar 13 17:01:31.100428 2020] [:error] [pid 13316:tid 140257819383552] [client 178.154.171.126:35097] [client 178.154.171.126] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "XmtZ@1qjv88O8iBlPKs9hwAAANw"]
...
2020-03-13 18:35:36
114.217.120.96 attackspam
Mar 12 22:49:13 mailman postfix/smtpd[22310]: warning: unknown[114.217.120.96]: SASL LOGIN authentication failed: authentication failure
2020-03-13 18:26:25
125.25.138.154 attackbotsspam
DATE:2020-03-13 04:48:40, IP:125.25.138.154, PORT:1433 - MSSQL brute force auth on a honeypot server (epe-dc)
2020-03-13 18:49:18
123.207.249.185 attackbots
WordPress XMLRPC scan :: 123.207.249.185 0.156 - [13/Mar/2020:03:48:22  0000] www.[censored_1] "GET /xmlrpc.php HTTP/1.1" 405 53 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0" "HTTP/1.1"
2020-03-13 18:58:16
192.241.238.175 attackspam
Scanning
2020-03-13 18:30:21
179.61.185.90 attackspam
Chat Spam
2020-03-13 18:44:30
79.2.90.15 attackbotsspam
scan z
2020-03-13 18:43:42

Recently Reported IPs

104.21.5.129 104.21.5.136 104.21.5.137 100.67.27.116
104.21.5.139 104.21.5.140 104.21.5.142 104.21.5.146
104.21.5.147 104.21.5.15 104.21.5.151 104.21.5.153
104.21.5.155 104.21.5.156 104.21.5.157 104.21.5.158
104.21.5.16 104.21.5.160 104.21.5.161 104.21.5.163