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

;; QUESTION SECTION:
;104.18.5.38.			IN	A

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

;; Query time: 26 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 13:53:12 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 38.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 38.5.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
199.204.45.193 attackbots
Feb  1 14:16:33 ms-srv sshd[18692]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=199.204.45.193
Feb  1 14:16:34 ms-srv sshd[18692]: Failed password for invalid user steven from 199.204.45.193 port 44542 ssh2
2020-02-03 00:11:53
80.66.81.86 attackbotsspam
Feb  2 16:49:12 relay postfix/smtpd\[9808\]: warning: unknown\[80.66.81.86\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb  2 16:50:45 relay postfix/smtpd\[9808\]: warning: unknown\[80.66.81.86\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb  2 16:51:06 relay postfix/smtpd\[30829\]: warning: unknown\[80.66.81.86\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb  2 17:05:49 relay postfix/smtpd\[9811\]: warning: unknown\[80.66.81.86\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb  2 17:06:08 relay postfix/smtpd\[9809\]: warning: unknown\[80.66.81.86\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-02-03 00:14:50
211.143.68.235 attack
DATE:2020-02-02 16:09:32, IP:211.143.68.235, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2020-02-02 23:43:55
195.31.160.73 attackbots
Unauthorized connection attempt detected from IP address 195.31.160.73 to port 2220 [J]
2020-02-02 23:38:57
195.222.163.54 attackbotsspam
Nov 28 15:04:03 ms-srv sshd[15130]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.222.163.54
Nov 28 15:04:04 ms-srv sshd[15130]: Failed password for invalid user Taito from 195.222.163.54 port 35146 ssh2
2020-02-03 00:00:35
185.176.27.178 attackbotsspam
Feb  2 16:59:22 debian-2gb-nbg1-2 kernel: \[2918416.119128\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.178 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=3365 PROTO=TCP SPT=49146 DPT=11125 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-03 00:08:18
217.57.145.116 attack
DATE:2020-02-02 16:09:36, IP:217.57.145.116, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2020-02-02 23:31:11
81.218.160.29 attackbots
Honeypot attack, port: 81, PTR: bzq-218-160-29.red.bezeqint.net.
2020-02-02 23:47:29
195.218.144.234 attack
Sep 20 20:24:34 ms-srv sshd[64954]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.218.144.234
Sep 20 20:24:36 ms-srv sshd[64954]: Failed password for invalid user lujanka from 195.218.144.234 port 37399 ssh2
2020-02-03 00:04:59
138.68.82.194 attack
Feb  2 16:09:29 mout sshd[19314]: Invalid user uftp from 138.68.82.194 port 48092
2020-02-02 23:46:59
195.22.239.226 attack
Apr 27 12:05:40 ms-srv sshd[56901]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.22.239.226
Apr 27 12:05:41 ms-srv sshd[56901]: Failed password for invalid user demo from 195.22.239.226 port 33840 ssh2
2020-02-03 00:03:10
213.149.169.44 attackspambots
DATE:2020-02-02 16:09:35, IP:213.149.169.44, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2020-02-02 23:37:09
202.137.141.240 attackspam
DATE:2020-02-02 16:09:16, IP:202.137.141.240, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2020-02-03 00:13:06
202.229.120.90 attackbotsspam
Unauthorized connection attempt detected from IP address 202.229.120.90 to port 2220 [J]
2020-02-02 23:58:22
61.185.131.172 attack
Feb  2 16:09:18 debian-2gb-nbg1-2 kernel: \[2915412.234928\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=61.185.131.172 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=6108 PROTO=TCP SPT=49677 DPT=1433 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-03 00:06:57

Recently Reported IPs

104.18.5.198 104.18.6.135 104.18.6.131 109.89.96.216
105.112.81.186 104.18.6.147 104.18.6.173 104.18.6.183
104.18.6.77 104.18.65.54 104.18.66.54 104.18.66.74
104.18.7.131 104.18.6.97 104.18.7.135 104.18.7.147
104.18.7.183 104.18.67.74 105.112.81.202 104.18.7.77