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:
IP Type Details Datetime
104.18.50.120 attack
*** Phishing website that camouflaged Amazon.com.
(redirect from)
https://subscriber.jglboots.com/
domain: subscriber.jglboots.com
IP v6 address: 2606:4700:3037::6812:3378 / 2606:4700:3033::6812:3278
IP v4 address: 104.18.50.120 / 104.18.51.120
location: USA
hosting: Cloudflare, Inc
web: https://www.cloudflare.com/abuse
abuse contact: abuse@cloudflare.com, abuse+law@cloudflare.com, rir@cloudflare.com
(redirect to)
https://counts-pontis-name-flare-and-safty.telemagico.com/
domain: counts-pontis-name-flare-and-safty.telemagico.com
IP v6 address: 2606:4700:3030::6818:62f1 / 2606:4700:3033::6818:63f1
IP v4 address: 104.24.99.241 / 104.24.98.241
location: USA
hosting: Cloudflare, Inc
web: https://www.cloudflare.com/abuse
abuse contact: abuse@cloudflare.com, abuse+law@cloudflare.com, rir@cloudflare.com
2020-05-04 03:15:46
104.18.54.70 spam
Used undred times per day for SPAM, PHISHING, SCAM and SEXE on STOLLEN list we don't know where without our agreement, as usual with LIERS and ROBERS !
Especially by namecheap.com with creatensend.com ?
https://www.mywot.com/scorecard/creatensend.com
https://www.mywot.com/scorecard/namecheap.com
Or uniregistry.com with casinovips.com ?
https://www.mywot.com/scorecard/casinovips.com
https://www.mywot.com/scorecard/uniregistry.com
And the same few hours before...
By GoDaddy.com, une autre SOUS MERDE adepte d'ESCROCS commebonusmasters.com...
https://www.mywot.com/scorecard/bonusmasters.com
https://www.mywot.com/scorecard/godaddy.com
2020-02-20 05:28:25
104.18.53.191 attack
*** Phishing website that camouflaged Google.
https://google-chrome.doysstv.com/?index
2020-01-04 20:34:01
104.18.52.191 attackspambots
*** Phishing website that camouflaged Google.
https://google-chrome.doysstv.com/?index
2020-01-04 18:36:35
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.18.5.58
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44248
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.18.5.58.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 01:54:30 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 58.5.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.5.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
155.4.255.138 attack
fire
2019-08-09 11:53:05
159.65.225.184 attack
Automatic report - Banned IP Access
2019-08-09 11:24:35
202.163.126.134 attack
Aug  9 03:35:45 server sshd\[1378\]: Invalid user osmc from 202.163.126.134 port 59455
Aug  9 03:35:45 server sshd\[1378\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.163.126.134
Aug  9 03:35:46 server sshd\[1378\]: Failed password for invalid user osmc from 202.163.126.134 port 59455 ssh2
Aug  9 03:40:59 server sshd\[9477\]: Invalid user ali from 202.163.126.134 port 55917
Aug  9 03:40:59 server sshd\[9477\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.163.126.134
2019-08-09 11:57:43
120.148.169.152 attackbotsspam
Aug  8 23:46:59 legacy sshd[19771]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.148.169.152
Aug  8 23:46:59 legacy sshd[19772]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.148.169.152
Aug  8 23:47:00 legacy sshd[19771]: Failed password for invalid user pi from 120.148.169.152 port 56678 ssh2
Aug  8 23:47:01 legacy sshd[19772]: Failed password for invalid user pi from 120.148.169.152 port 56686 ssh2
...
2019-08-09 11:29:03
147.135.208.69 attack
2019-08-09T03:19:43.430377abusebot-2.cloudsearch.cf sshd\[20678\]: Invalid user test from 147.135.208.69 port 38860
2019-08-09 11:43:50
185.94.111.1 attackspam
09.08.2019 03:14:42 Connection to port 17 blocked by firewall
2019-08-09 12:00:26
191.53.237.232 attack
Aug  8 17:46:51 web1 postfix/smtpd[13314]: warning: unknown[191.53.237.232]: SASL PLAIN authentication failed: authentication failure
...
2019-08-09 11:34:34
104.248.221.194 attackspambots
Aug  9 03:20:21 [munged] sshd[26870]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.221.194
2019-08-09 12:01:57
177.129.205.222 attack
Aug  8 17:46:38 web1 postfix/smtpd[13314]: warning: unknown[177.129.205.222]: SASL PLAIN authentication failed: authentication failure
...
2019-08-09 11:41:12
58.85.156.48 attack
Honeypot attack, port: 23, PTR: zaq3a559c30.zaq.ne.jp.
2019-08-09 12:00:52
66.70.130.149 attackspambots
Aug  9 02:44:55 SilenceServices sshd[24091]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.70.130.149
Aug  9 02:44:58 SilenceServices sshd[24091]: Failed password for invalid user art from 66.70.130.149 port 41920 ssh2
Aug  9 02:49:55 SilenceServices sshd[30007]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.70.130.149
2019-08-09 11:46:26
41.72.219.102 attackspambots
ssh failed login
2019-08-09 11:53:28
81.22.45.148 attack
Aug  9 04:28:36 h2177944 kernel: \[3641535.178866\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.148 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=3906 PROTO=TCP SPT=44617 DPT=8586 WINDOW=1024 RES=0x00 SYN URGP=0 
Aug  9 04:34:56 h2177944 kernel: \[3641914.840676\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.148 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=39098 PROTO=TCP SPT=44617 DPT=8180 WINDOW=1024 RES=0x00 SYN URGP=0 
Aug  9 04:45:30 h2177944 kernel: \[3642549.410407\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.148 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=58848 PROTO=TCP SPT=44617 DPT=8652 WINDOW=1024 RES=0x00 SYN URGP=0 
Aug  9 05:02:40 h2177944 kernel: \[3643578.495604\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.148 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=22235 PROTO=TCP SPT=44617 DPT=8824 WINDOW=1024 RES=0x00 SYN URGP=0 
Aug  9 05:26:25 h2177944 kernel: \[3645003.685929\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.148 DST=85.214.117.9 LEN=4
2019-08-09 11:45:35
157.230.42.76 attack
SSH-BruteForce
2019-08-09 11:26:08
178.62.202.119 attackbots
fire
2019-08-09 11:26:48

Recently Reported IPs

104.18.5.28 104.18.5.73 104.21.65.55 104.18.5.74
104.18.5.70 104.18.5.77 104.18.5.46 204.108.199.78
104.18.6.104 104.18.5.85 104.18.5.80 104.18.5.83
104.18.6.107 104.18.6.112 104.18.5.92 104.18.6.106
104.18.6.119 104.18.6.116 104.21.65.58 104.18.6.12