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.7.4 attackspam
[DoS Attack: SYN/ACK Scan] from source: 104.18.7.4, port 443, Friday, July 31, 2020 22:27:58
2020-08-01 06:05:57
104.18.70.149 attack
"MarketingPromoSystems, 8 The Green Suite #5828 Dover DE" 185.230.46.95 - phishing redirect www1.innovationaltech.xyz
2020-05-24 22:42:26
104.18.71.149 attack
"MarketingPromoSystems, 8 The Green Suite #5828 Dover DE" 185.230.46.95 - phishing redirect www1.innovationaltech.xyz
2020-05-24 22:11:41
104.18.72.149 attackspam
"MarketingPromoSystems, 8 The Green Suite #5828 Dover DE" 185.230.46.95 - phishing redirect www1.innovationaltech.xyz
2020-05-24 21:44:55
104.18.70.28 spam
AGAIN and AGAIN and ALWAYS the same REGISTRAR as 1api.net TO STOP IMMEDIATELY for keeping SPAMMERS, LIERS, ROBERS and else since too many years ! The cheapest service, as usual...
Dossier transmis aux autorités Européennes et Françaises pour CONDAMNATION à 750 € par POURRIEL émis les SOUS MERDES, OK ?

From: Joka 
Date: Wed, 18 Mar 2020 16:46:18 +0000
Subject: LE CASINO JOKA. =?utf-8?b?T8OZ?= LES FORTUNES SE PROFILENT
Message-Id: <4WMA.BA1D.F33KVOH670.20200318164618859@bestoffer-today.com>

live@bestoffer-today.com which send to « https://bestoffer-today.com/4WMA-BA1D-F33KVOH670/uauto.aspx » to BURN / CLOSE / DELETTE / STOP IMMEDIATELY for SPAM, PHISHING and SCAM on STOLLEN List ! ! !

bestoffer-today.com => 1api.net

bestoffer-today.com => 104.16.209.86

104.16.209.86 => cloudflare.com AS USUAL...

1api.net => 84.200.110.124

84.200.110.124 => accelerated.de

live@bestoffer-today.com => 94.143.106.199

94.143.106.199 => dotmailer.com

dotmailer.com => 104.18.70.28

104.18.70.28 => cloudflare.com AS USUAL...

dotmailer.com send to dotdigital.com

dotdigital.com => 104.19.144.113

104.19.144.113 => cloudflare.com

https://www.mywot.com/scorecard/dotmailer.com

https://www.mywot.com/scorecard/dotdigital.com

https://www.mywot.com/scorecard/bestoffer-today.com

https://www.mywot.com/scorecard/1api.net AS USUAL...

https://en.asytech.cn/check-ip/104.16.209.86

https://en.asytech.cn/check-ip/84.200.110.124

https://en.asytech.cn/check-ip/94.143.106.199

https://en.asytech.cn/check-ip/104.18.70.28

https://en.asytech.cn/check-ip/104.19.144.113
2020-03-19 05:04:23
104.18.70.106 attack
siteaudit.crawler.semrush.com - - \[27/Oct/2019:04:48:48 +0100\] "GET /robots.txt HTTP/1.1" 200 4578 "-" "Mozilla/5.0 \(compatible\; Googlebot/2.1\; +http://www.google.com/bot.html\)"
siteaudit.crawler.semrush.com - - \[27/Oct/2019:04:48:49 +0100\] "GET /galerie/villa-bunterkund.html HTTP/1.1" 200 10713 "-" "Mozilla/5.0 \(compatible\; Googlebot/2.1\; +http://www.google.com/bot.html\)"
siteaudit.crawler.semrush.com - - \[27/Oct/2019:04:48:55 +0100\] "GET / HTTP/1.1" 200 9534 "-" "Mozilla/5.0 \(compatible\; Googlebot/2.1\; +http://www.google.com/bot.html\)"
...
2019-10-27 17:27:20
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.18.7.240
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44645
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.18.7.240.			IN	A

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

;; Query time: 24 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 05:54:14 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 240.7.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 240.7.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
218.150.220.226 attackbots
2019-10-24T06:54:44.966235abusebot-5.cloudsearch.cf sshd\[15899\]: Invalid user bjorn from 218.150.220.226 port 60578
2019-10-24 14:58:06
80.211.0.160 attack
Automatic report - Banned IP Access
2019-10-24 15:16:48
188.235.146.137 attack
Automatic report - Banned IP Access
2019-10-24 15:25:08
89.248.168.217 attack
Scanning (more than 2 packets) random ports - tries to find possible vulnerable services
2019-10-24 14:50:40
106.12.130.148 attackspambots
Oct 24 02:46:52 TORMINT sshd\[15551\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.130.148  user=root
Oct 24 02:46:53 TORMINT sshd\[15551\]: Failed password for root from 106.12.130.148 port 58420 ssh2
Oct 24 02:52:43 TORMINT sshd\[15719\]: Invalid user yk from 106.12.130.148
Oct 24 02:52:43 TORMINT sshd\[15719\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.130.148
...
2019-10-24 14:58:28
103.208.220.226 attackbotsspam
Oct 24 03:51:46 thevastnessof sshd[2994]: Failed password for root from 103.208.220.226 port 51624 ssh2
...
2019-10-24 15:10:23
118.70.170.243 attack
445/tcp
[2019-10-24]1pkt
2019-10-24 15:09:38
49.88.112.77 attackbotsspam
Oct 24 10:17:04 pkdns2 sshd\[63816\]: Failed password for root from 49.88.112.77 port 53172 ssh2Oct 24 10:17:07 pkdns2 sshd\[63816\]: Failed password for root from 49.88.112.77 port 53172 ssh2Oct 24 10:17:09 pkdns2 sshd\[63816\]: Failed password for root from 49.88.112.77 port 53172 ssh2Oct 24 10:20:43 pkdns2 sshd\[63982\]: Failed password for root from 49.88.112.77 port 21386 ssh2Oct 24 10:22:59 pkdns2 sshd\[64044\]: Failed password for root from 49.88.112.77 port 45434 ssh2Oct 24 10:23:01 pkdns2 sshd\[64044\]: Failed password for root from 49.88.112.77 port 45434 ssh2
...
2019-10-24 15:29:57
106.12.16.107 attack
Oct 23 19:41:13 sachi sshd\[18672\]: Invalid user dingman136119 from 106.12.16.107
Oct 23 19:41:13 sachi sshd\[18672\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.16.107
Oct 23 19:41:14 sachi sshd\[18672\]: Failed password for invalid user dingman136119 from 106.12.16.107 port 57380 ssh2
Oct 23 19:45:54 sachi sshd\[19054\]: Invalid user 123 from 106.12.16.107
Oct 23 19:45:54 sachi sshd\[19054\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.16.107
2019-10-24 15:17:40
109.224.37.85 attack
postfix
2019-10-24 15:06:38
14.169.243.154 attackbots
445/tcp
[2019-10-24]1pkt
2019-10-24 15:23:33
116.97.219.210 attack
445/tcp
[2019-10-24]1pkt
2019-10-24 14:52:58
171.244.140.174 attackbots
Oct 24 10:05:49 server sshd\[11509\]: Invalid user 1 from 171.244.140.174 port 11191
Oct 24 10:05:49 server sshd\[11509\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.244.140.174
Oct 24 10:05:51 server sshd\[11509\]: Failed password for invalid user 1 from 171.244.140.174 port 11191 ssh2
Oct 24 10:10:41 server sshd\[1333\]: Invalid user aaaaaa from 171.244.140.174 port 30246
Oct 24 10:10:41 server sshd\[1333\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.244.140.174
2019-10-24 15:22:45
36.233.151.144 attack
23/tcp
[2019-10-24]1pkt
2019-10-24 14:56:41
35.240.222.249 attackspambots
WordPress wp-login brute force :: 35.240.222.249 0.120 BYPASS [24/Oct/2019:16:08:45  1100] [censored_1] "POST /wp-login.php HTTP/1.1" 200 3972 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-10-24 15:10:02

Recently Reported IPs

104.18.7.23 104.18.7.25 104.18.7.29 104.18.7.33
104.18.7.60 104.18.7.68 104.18.7.8 104.18.7.92
104.18.70.92 182.180.44.58 104.18.79.2 104.18.8.127
104.18.8.13 104.18.8.131 104.18.8.134 104.18.8.137
104.18.8.15 104.18.8.152 104.18.8.164 104.18.8.165