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

;; QUESTION SECTION:
;104.18.21.58.			IN	A

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

;; Query time: 47 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Apr 03 05:17:10 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 58.21.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 58.21.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
14.3.12.191 attackspambots
445/tcp
[2019-07-12]1pkt
2019-07-12 20:46:37
218.156.38.130 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2019-07-12 20:59:21
46.161.27.117 attackspambots
3389BruteforceIDS
2019-07-12 20:32:19
45.248.133.36 attackbotsspam
Jul 12 14:37:31 localhost sshd\[22685\]: Invalid user rafael from 45.248.133.36 port 37150
Jul 12 14:37:31 localhost sshd\[22685\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.248.133.36
Jul 12 14:37:33 localhost sshd\[22685\]: Failed password for invalid user rafael from 45.248.133.36 port 37150 ssh2
2019-07-12 20:45:29
188.75.179.90 attackspam
Brute force attempt
2019-07-12 20:51:12
114.46.101.149 attack
37215/tcp
[2019-07-12]1pkt
2019-07-12 20:23:59
117.2.130.16 attackspambots
Unauthorized connection attempt from IP address 117.2.130.16 on Port 445(SMB)
2019-07-12 20:12:59
132.232.16.200 attack
WordPress brute force
2019-07-12 20:23:13
138.197.165.64 attackspambots
WordPress brute force
2019-07-12 20:15:57
13.91.83.117 attackbots
WordPress brute force
2019-07-12 20:14:32
138.197.116.132 attackspambots
WordPress brute force
2019-07-12 20:17:35
186.232.14.60 attackbots
mail.log:Jun 27 18:17:42 mail postfix/smtpd[20978]: warning: unknown[186.232.14.60]: SASL PLAIN authentication failed: authentication failure
2019-07-12 20:18:37
27.194.94.134 attack
23/tcp
[2019-07-12]1pkt
2019-07-12 20:55:07
124.41.211.139 attackbots
WordPress brute force
2019-07-12 20:26:03
190.105.213.223 attackbots
2019-07-12T13:30:33.866918beta postfix/smtpd[23536]: warning: host223.190-105-213.sitsanetworks.net[190.105.213.223]: SASL LOGIN authentication failed: authentication failure
2019-07-12T13:30:37.683457beta postfix/smtpd[23536]: warning: host223.190-105-213.sitsanetworks.net[190.105.213.223]: SASL LOGIN authentication failed: authentication failure
2019-07-12T13:30:41.725677beta postfix/smtpd[23536]: warning: host223.190-105-213.sitsanetworks.net[190.105.213.223]: SASL LOGIN authentication failed: authentication failure
2019-07-12T13:30:44.984612beta postfix/smtpd[23536]: warning: host223.190-105-213.sitsanetworks.net[190.105.213.223]: SASL LOGIN authentication failed: authentication failure
2019-07-12T13:30:49.394906beta postfix/smtpd[23536]: warning: host223.190-105-213.sitsanetworks.net[190.105.213.223]: SASL LOGIN authentication failed: authentication failure
...
2019-07-12 20:50:49

Recently Reported IPs

104.18.204.85 104.18.223.34 104.18.223.49 104.18.224.49
104.18.226.99 104.18.227.99 104.18.231.51 104.18.232.51
104.18.234.76 104.18.24.62 104.18.243.105 104.18.244.218
104.18.245.218 104.18.247.48 104.18.248.48 104.18.25.62
104.18.28.53 104.18.29.53 104.18.30.156 104.18.30.193