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

;; QUESTION SECTION:
;104.18.10.29.			IN	A

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

;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Mar 06 07:08:40 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 29.10.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.10.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
218.92.0.135 attack
Brute-force attempt banned
2019-12-28 02:24:14
118.97.77.130 attack
SIP/5060 Probe, BF, Hack -
2019-12-28 02:27:32
175.204.91.168 attackspam
Unauthorized connection attempt detected from IP address 175.204.91.168 to port 22
2019-12-28 02:38:08
113.125.58.0 attackspambots
2019-12-27T16:53:19.031215abusebot-4.cloudsearch.cf sshd[8770]: Invalid user littau from 113.125.58.0 port 35230
2019-12-27T16:53:19.039435abusebot-4.cloudsearch.cf sshd[8770]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.125.58.0
2019-12-27T16:53:19.031215abusebot-4.cloudsearch.cf sshd[8770]: Invalid user littau from 113.125.58.0 port 35230
2019-12-27T16:53:21.248069abusebot-4.cloudsearch.cf sshd[8770]: Failed password for invalid user littau from 113.125.58.0 port 35230 ssh2
2019-12-27T16:57:31.617610abusebot-4.cloudsearch.cf sshd[8772]: Invalid user oysapa from 113.125.58.0 port 51218
2019-12-27T16:57:31.624506abusebot-4.cloudsearch.cf sshd[8772]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.125.58.0
2019-12-27T16:57:31.617610abusebot-4.cloudsearch.cf sshd[8772]: Invalid user oysapa from 113.125.58.0 port 51218
2019-12-27T16:57:33.763533abusebot-4.cloudsearch.cf sshd[8772]: Failed password 
...
2019-12-28 02:39:04
27.254.130.69 attackbots
Repeated failed SSH attempt
2019-12-28 02:43:28
185.2.4.33 attackspam
Fri Dec 27 16:50:04 2019 \[pid 25796\] \[group\] FTP response: Client "185.2.4.33", "530 Permission denied."
Fri Dec 27 16:50:06 2019 \[pid 25806\] \[forest\] FTP response: Client "185.2.4.33", "530 Permission denied."
Fri Dec 27 16:50:08 2019 \[pid 25808\] \[house\] FTP response: Client "185.2.4.33", "530 Permission denied."
2019-12-28 02:29:05
118.99.180.218 attack
Dec 27 15:48:13 Ubuntu-1404-trusty-64-minimal sshd\[8325\]: Invalid user bluehost from 118.99.180.218
Dec 27 15:48:13 Ubuntu-1404-trusty-64-minimal sshd\[8325\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.99.180.218
Dec 27 15:48:14 Ubuntu-1404-trusty-64-minimal sshd\[8325\]: Failed password for invalid user bluehost from 118.99.180.218 port 33593 ssh2
Dec 27 15:49:20 Ubuntu-1404-trusty-64-minimal sshd\[8588\]: Invalid user nagios from 118.99.180.218
Dec 27 15:49:20 Ubuntu-1404-trusty-64-minimal sshd\[8588\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.99.180.218
2019-12-28 02:30:34
182.150.58.161 attack
12/27/2019-15:49:40.752067 182.150.58.161 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-12-28 02:15:20
94.249.81.206 attackbots
Dec 27 15:48:57 debian-2gb-nbg1-2 kernel: \[1110860.559586\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=94.249.81.206 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=50 ID=20897 PROTO=TCP SPT=44140 DPT=23 WINDOW=33857 RES=0x00 SYN URGP=0
2019-12-28 02:53:11
154.209.252.222 attackbotsspam
The IP has triggered Cloudflare WAF. CF-Ray: 54ba1e7ceadd32db | WAF_Rule_ID: 53b8357af6d244d3a132bcf913c3a388 | WAF_Kind: firewall | CF_Action: drop | Country: HK | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: blog.skk.moe | User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0 | CF_DC: HKG. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-28 02:29:47
118.193.21.186 attackbotsspam
12/27/2019-18:58:12.520424 118.193.21.186 Protocol: 6 ET SCAN Suspicious inbound to PostgreSQL port 5432
2019-12-28 02:40:37
129.205.112.253 attack
Dec 27 16:11:47 localhost sshd\[16887\]: Invalid user emilie from 129.205.112.253 port 47408
Dec 27 16:11:47 localhost sshd\[16887\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.205.112.253
Dec 27 16:11:49 localhost sshd\[16887\]: Failed password for invalid user emilie from 129.205.112.253 port 47408 ssh2
2019-12-28 02:21:29
123.206.134.27 attack
Automatic report - Banned IP Access
2019-12-28 02:27:15
5.189.176.208 attackbots
WEB Masscan Scanner Activity
2019-12-28 02:30:54
112.135.233.72 attack
Unauthorised access (Dec 27) SRC=112.135.233.72 LEN=44 TTL=243 ID=50109 DF TCP DPT=23 WINDOW=14600 SYN
2019-12-28 02:42:35

Recently Reported IPs

104.18.10.223 104.18.104.8 104.18.105.59 104.18.106.59
104.18.11.135 104.18.11.181 104.18.11.29 104.18.110.89
104.18.111.89 104.18.113.96 104.18.12.109 104.18.12.165
104.18.12.167 104.18.12.192 99.98.90.163 104.18.14.136
104.18.14.177 104.18.14.190 104.18.14.23 104.18.14.245