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

;; QUESTION SECTION:
;104.18.34.29.			IN	A

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

;; Query time: 117 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri May 27 07:42:56 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 29.34.18.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.34.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
210.177.223.252 attack
Scanned 3 times in the last 24 hours on port 22
2020-04-24 08:05:18
223.171.46.146 attackspambots
leo_www
2020-04-24 12:05:20
103.74.122.145 attack
WordPress brute force
2020-04-24 08:00:38
211.20.109.47 attackbots
trying to access non-authorized port
2020-04-24 08:15:05
178.62.36.116 attack
Apr 24 03:50:13 marvibiene sshd[14970]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.36.116  user=root
Apr 24 03:50:15 marvibiene sshd[14970]: Failed password for root from 178.62.36.116 port 40830 ssh2
Apr 24 03:58:26 marvibiene sshd[15018]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.36.116  user=root
Apr 24 03:58:29 marvibiene sshd[15018]: Failed password for root from 178.62.36.116 port 43220 ssh2
...
2020-04-24 12:07:02
192.161.179.194 attackspam
20/4/23@23:58:21: FAIL: Alarm-Network address from=192.161.179.194
20/4/23@23:58:21: FAIL: Alarm-Network address from=192.161.179.194
...
2020-04-24 12:13:08
192.241.238.224 attackbotsspam
port scan and connect, tcp 22 (ssh)
2020-04-24 08:10:10
36.67.197.52 attackspam
2020-04-24 02:27:55,089 fail2ban.actions        [22360]: NOTICE  [sshd] Ban 36.67.197.52
2020-04-24 03:02:12,469 fail2ban.actions        [22360]: NOTICE  [sshd] Ban 36.67.197.52
2020-04-24 04:46:59,218 fail2ban.actions        [22360]: NOTICE  [sshd] Ban 36.67.197.52
2020-04-24 05:22:57,584 fail2ban.actions        [22360]: NOTICE  [sshd] Ban 36.67.197.52
2020-04-24 05:59:22,578 fail2ban.actions        [22360]: NOTICE  [sshd] Ban 36.67.197.52
...
2020-04-24 12:01:25
202.88.252.53 attackspam
$f2bV_matches
2020-04-24 12:01:37
101.89.147.85 attack
k+ssh-bruteforce
2020-04-24 12:15:00
202.134.0.9 attackspam
Multiport scan : 5 ports scanned 1604 2834 5472 18950 26265
2020-04-24 08:07:40
198.108.67.87 attack
Port scan(s) denied
2020-04-24 08:17:56
78.128.113.178 attackspam
1 attempts against mh-modsecurity-ban on sand
2020-04-24 08:08:42
188.166.251.87 attackspambots
Invalid user vc from 188.166.251.87 port 59013
2020-04-24 08:11:47
196.52.43.116 attackspambots
82/tcp 8333/tcp 6379/tcp...
[2020-02-25/04-22]50pkt,40pt.(tcp),1pt.(udp)
2020-04-24 08:11:23

Recently Reported IPs

104.18.34.245 104.18.35.10 104.18.35.106 104.18.35.249
104.18.36.19 104.18.38.151 104.18.39.229 104.18.39.231
104.18.4.173 104.18.40.12 104.18.40.123 104.18.40.134
104.18.40.135 104.18.40.209 104.18.40.77 104.18.41.134
104.18.41.154 104.18.41.16 181.34.142.250 104.20.161.55