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

;; QUESTION SECTION:
;104.21.5.29.			IN	A

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

;; Query time: 55 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 23:26:11 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 29.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 29.5.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
106.12.117.195 attackbotsspam
Lines containing failures of 106.12.117.195
Jun  3 12:08:21 keyhelp sshd[32465]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.117.195  user=r.r
Jun  3 12:08:23 keyhelp sshd[32465]: Failed password for r.r from 106.12.117.195 port 35002 ssh2
Jun  3 12:08:23 keyhelp sshd[32465]: Received disconnect from 106.12.117.195 port 35002:11: Bye Bye [preauth]
Jun  3 12:08:23 keyhelp sshd[32465]: Disconnected from authenticating user r.r 106.12.117.195 port 35002 [preauth]
Jun  3 12:18:13 keyhelp sshd[1780]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.117.195  user=r.r
Jun  3 12:18:15 keyhelp sshd[1780]: Failed password for r.r from 106.12.117.195 port 43220 ssh2
Jun  3 12:18:15 keyhelp sshd[1780]: Received disconnect from 106.12.117.195 port 43220:11: Bye Bye [preauth]
Jun  3 12:18:15 keyhelp sshd[1780]: Disconnected from authenticating user r.r 106.12.117.195 port 43220 [preauth]

........
------------------------------
2020-06-04 03:35:37
91.243.210.117 attackbotsspam
1591184803 - 06/03/2020 13:46:43 Host: 91.243.210.117/91.243.210.117 Port: 445 TCP Blocked
2020-06-04 04:08:07
114.204.218.154 attackspambots
2020-06-03T20:12:47.009943ns386461 sshd\[14166\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.204.218.154  user=root
2020-06-03T20:12:48.998943ns386461 sshd\[14166\]: Failed password for root from 114.204.218.154 port 45997 ssh2
2020-06-03T20:24:27.770570ns386461 sshd\[25238\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.204.218.154  user=root
2020-06-03T20:24:29.192910ns386461 sshd\[25238\]: Failed password for root from 114.204.218.154 port 59948 ssh2
2020-06-03T20:28:03.724589ns386461 sshd\[28623\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.204.218.154  user=root
...
2020-06-04 04:12:24
216.218.206.124 attackbots
Jun  3 14:46:43 debian kernel: [87368.370645] [UFW BLOCK] IN=eth0 OUT= MAC=52:54:00:be:e4:65:08:e8:4f:6e:48:0c:08:00 SRC=216.218.206.124 DST=89.252.131.35 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=54321 PROTO=TCP SPT=33061 DPT=7547 WINDOW=65535 RES=0x00 SYN URGP=0
2020-06-04 04:07:50
192.129.175.216 attackspam
Jun  3 15:14:04 debian kernel: [89008.450573] [UFW BLOCK] IN=eth0 OUT= MAC=52:54:00:be:e4:65:08:e8:4f:6e:48:0c:08:00 SRC=192.129.175.216 DST=89.252.131.35 LEN=40 TOS=0x00 PREC=0x00 TTL=239 ID=54321 PROTO=TCP SPT=58586 DPT=85 WINDOW=65535 RES=0x00 SYN URGP=0
2020-06-04 03:51:31
173.254.247.48 attackspam
(From eric@talkwithwebvisitor.com) Good day, 

My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations

What for?  

Part of my job is to check out websites and the work you’ve done with drjenniferbrandon.com definitely stands out. 

It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality.

There is, however, a catch… more accurately, a question…

So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? 

More importantly, how do you make a connection with that person?

Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind.

Here’s a way to create INSTANT engagement that you may not have known about… 

Talk With Web Visitor is a software widget that’s works on your site, ready to capture a
2020-06-04 03:37:42
218.211.12.26 attackbots
SMB Server BruteForce Attack
2020-06-04 03:55:21
116.98.247.21 attackbots
SMB Server BruteForce Attack
2020-06-04 04:10:14
36.231.217.23 attack
 TCP (SYN) 36.231.217.23:62723 -> port 23, len 44
2020-06-04 03:56:11
93.176.179.138 attack
Automatic report - Port Scan Attack
2020-06-04 03:45:13
106.12.109.33 attackbotsspam
Jun  3 21:41:15 legacy sshd[24860]: Failed password for root from 106.12.109.33 port 35362 ssh2
Jun  3 21:42:28 legacy sshd[24924]: Failed password for root from 106.12.109.33 port 34480 ssh2
...
2020-06-04 03:52:30
118.25.134.204 attackbotsspam
20 attempts against mh-misbehave-ban on comet
2020-06-04 03:33:09
93.49.247.215 attackbots
firewall-block, port(s): 23/tcp
2020-06-04 03:43:35
113.199.164.76 attack
Unauthorized connection attempt detected from IP address 113.199.164.76 to port 23
2020-06-04 03:42:20
145.255.21.151 attackbots
Port probing on unauthorized port 445
2020-06-04 03:38:39

Recently Reported IPs

104.21.5.28 104.21.5.31 104.21.5.33 104.21.5.39
221.31.125.8 104.21.5.4 104.21.5.42 104.21.5.45
104.21.5.47 104.21.5.49 104.21.5.50 104.21.5.55
29.7.125.123 104.21.5.61 104.21.5.64 104.21.5.66
104.21.5.67 104.21.5.68 104.21.5.7 104.21.5.70