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
66.249.70.48 attack
TIME: Fri, 25 Sep 2020 17:36:22 -0300
 REQUEST: /.well-known/assetlinks.json
2020-09-27 01:01:57
66.249.70.48 attack
TIME: Fri, 25 Sep 2020 17:36:22 -0300
 REQUEST: /.well-known/assetlinks.json
2020-09-26 16:53:06
66.249.70.59 attack
SQL Injection
2020-08-08 02:36:20
66.249.70.76 attackspam
404 NOT FOUND
2020-06-07 01:00:40
66.249.70.9 attackbots
Automatic report - Banned IP Access
2020-05-30 23:24:50
66.249.70.11 attack
Automatic report - Banned IP Access
2020-05-30 23:21:03
66.249.70.32 attackbots
66.249.70.32 - - \[03/May/2020:05:50:20 +0200\] "GET /robots.txt HTTP/1.1" 404 162 "-" "Mozilla/5.0 \(compatible\; Googlebot/2.1\; +http://www.google.com/bot.html\)"
...
2020-05-03 17:17:51
66.249.70.60 attackbotsspam
...
2020-05-03 17:11:58
66.249.70.62 attackspam
Wordpress_Attack
2020-01-24 05:57:33
66.249.70.38 attackbots
66.249.70.38 - - [19/Jan/2020:07:55:18 -0500] "GET /?page=/etc/passwd&action=view&manufacturerID=36&productID=9621C10&linkID=13042 HTTP/1.1" 200 13126 "-" "Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.96 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"
...
2020-01-20 01:23:45
66.249.70.62 attack
Automatic report - Web App Attack
2019-11-06 01:16:28
66.249.70.11 attackbotsspam
404 NOT FOUND
2019-10-14 14:29:04
66.249.70.23 attackspambots
Lines containing failures of 66.249.70.23
/var/log/apache/pucorp.org.log:66.249.70.23 - - [06/Oct/2019:00:30:38 +0200] "GET /robots.txt HTTP/1.1" 200 5892 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +hxxp://www.google.com/bot.html)"
/var/log/apache/pucorp.org.log:66.249.70.23 - - [06/Oct/2019:00:30:38 +0200] "GET / HTTP/1.1" 200 11492 "-" "Mozilla/5.0 (Linux; user 6.0.1; Nexus 5X Build/MMB29P) AppleWebKhostname/537.36 (KHTML, like Gecko) Chrome/41.0.2272.96 Mobile Safari/537.36 (compatible; Googlebot/2.1; +hxxp://www.google.com/bot.html)"


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=66.249.70.23
2019-10-07 20:02:30
66.249.70.9 attack
Automatic report - Banned IP Access
2019-09-26 15:02:58
66.249.70.7 attackspam
WordpressAttack
2019-09-02 05:45:32
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 66.249.70.6
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28365
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;66.249.70.6.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 18:07:38 CST 2022
;; MSG SIZE  rcvd: 104
Host info
6.70.249.66.in-addr.arpa domain name pointer crawl-66-249-70-6.googlebot.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
6.70.249.66.in-addr.arpa	name = crawl-66-249-70-6.googlebot.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
37.187.140.206 attackbots
37.187.140.206 - - \[28/Oct/2019:06:58:01 +0000\] "POST /wp-login.php HTTP/1.1" 200 4358 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
37.187.140.206 - - \[28/Oct/2019:06:58:02 +0000\] "POST /xmlrpc.php HTTP/1.1" 200 403 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
...
2019-10-28 15:07:33
223.206.247.141 attackbotsspam
445/tcp
[2019-10-28]1pkt
2019-10-28 14:53:37
81.22.45.107 attackspambots
Oct 28 07:32:21 mc1 kernel: \[3530671.829964\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=81.22.45.107 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=60605 PROTO=TCP SPT=46683 DPT=31200 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 28 07:36:01 mc1 kernel: \[3530891.693623\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=81.22.45.107 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=2381 PROTO=TCP SPT=46683 DPT=30903 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 28 07:39:35 mc1 kernel: \[3531105.550171\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=81.22.45.107 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=53695 PROTO=TCP SPT=46683 DPT=31347 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-10-28 14:40:35
178.128.150.158 attackbots
(sshd) Failed SSH login from 178.128.150.158 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct 28 04:39:40 server2 sshd[4108]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.150.158  user=mysql
Oct 28 04:39:42 server2 sshd[4108]: Failed password for mysql from 178.128.150.158 port 35608 ssh2
Oct 28 04:49:36 server2 sshd[4363]: Invalid user cvsuser from 178.128.150.158 port 52796
Oct 28 04:49:38 server2 sshd[4363]: Failed password for invalid user cvsuser from 178.128.150.158 port 52796 ssh2
Oct 28 04:53:00 server2 sshd[4488]: Invalid user vz from 178.128.150.158 port 35076
2019-10-28 14:36:21
121.122.109.21 attackbotsspam
445/tcp
[2019-10-28]1pkt
2019-10-28 15:03:39
192.3.215.202 attack
1,63-14/07 [bc02/m44] PostRequest-Spammer scoring: rome
2019-10-28 14:57:44
218.207.123.110 attackspam
23/tcp
[2019-10-28]1pkt
2019-10-28 14:39:47
115.238.236.74 attackspambots
Oct 28 07:47:56 vps691689 sshd[20999]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.238.236.74
Oct 28 07:47:58 vps691689 sshd[20999]: Failed password for invalid user ipko from 115.238.236.74 port 18605 ssh2
...
2019-10-28 14:53:58
3.86.177.77 attackspam
Oct 28 05:50:18 lola sshd[6532]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-3-86-177-77.compute-1.amazonaws.com  user=r.r
Oct 28 05:50:20 lola sshd[6532]: Failed password for r.r from 3.86.177.77 port 34092 ssh2
Oct 28 05:50:20 lola sshd[6532]: Received disconnect from 3.86.177.77: 11: Bye Bye [preauth]
Oct 28 06:14:02 lola sshd[9218]: Invalid user trendimsa1.0 from 3.86.177.77
Oct 28 06:14:02 lola sshd[9218]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-3-86-177-77.compute-1.amazonaws.com 
Oct 28 06:14:04 lola sshd[9218]: Failed password for invalid user trendimsa1.0 from 3.86.177.77 port 53882 ssh2
Oct 28 06:14:04 lola sshd[9218]: Received disconnect from 3.86.177.77: 11: Bye Bye [preauth]
Oct 28 06:17:12 lola sshd[9857]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-3-86-177-77.compute-1.amazonaws.com  user=r.r
Oct 28 06:17:13 ........
-------------------------------
2019-10-28 14:57:09
156.199.218.187 attackspam
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/156.199.218.187/ 
 
 EG - 1H : (337)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : EG 
 NAME ASN : ASN8452 
 
 IP : 156.199.218.187 
 
 CIDR : 156.199.192.0/18 
 
 PREFIX COUNT : 833 
 
 UNIQUE IP COUNT : 7610368 
 
 
 ATTACKS DETECTED ASN8452 :  
  1H - 13 
  3H - 37 
  6H - 85 
 12H - 176 
 24H - 327 
 
 DateTime : 2019-10-28 04:52:45 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-10-28 14:48:21
180.182.245.93 attackspambots
23/tcp
[2019-10-28]1pkt
2019-10-28 14:48:06
103.212.235.182 attack
Oct 28 06:41:28 localhost sshd\[32874\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.212.235.182  user=root
Oct 28 06:41:31 localhost sshd\[32874\]: Failed password for root from 103.212.235.182 port 60710 ssh2
Oct 28 06:46:02 localhost sshd\[32988\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.212.235.182  user=root
Oct 28 06:46:04 localhost sshd\[32988\]: Failed password for root from 103.212.235.182 port 42526 ssh2
Oct 28 06:50:39 localhost sshd\[33107\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.212.235.182  user=root
...
2019-10-28 14:56:04
37.70.132.170 attackbotsspam
Oct 28 02:02:20 Tower sshd[30016]: Connection from 37.70.132.170 port 37829 on 192.168.10.220 port 22
Oct 28 02:02:24 Tower sshd[30016]: Invalid user wh from 37.70.132.170 port 37829
Oct 28 02:02:24 Tower sshd[30016]: error: Could not get shadow information for NOUSER
Oct 28 02:02:24 Tower sshd[30016]: Failed password for invalid user wh from 37.70.132.170 port 37829 ssh2
Oct 28 02:02:24 Tower sshd[30016]: Received disconnect from 37.70.132.170 port 37829:11: Bye Bye [preauth]
Oct 28 02:02:24 Tower sshd[30016]: Disconnected from invalid user wh 37.70.132.170 port 37829 [preauth]
2019-10-28 14:44:24
222.186.190.92 attackbotsspam
Oct 28 07:51:28 dedicated sshd[26631]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.190.92  user=root
Oct 28 07:51:30 dedicated sshd[26631]: Failed password for root from 222.186.190.92 port 52236 ssh2
2019-10-28 14:57:29
176.105.203.85 attack
23/tcp
[2019-10-28]1pkt
2019-10-28 14:54:38

Recently Reported IPs

66.249.70.78 66.249.70.80 66.249.70.159 66.249.70.8
66.249.70.150 66.249.73.124 66.249.74.93 66.249.72.33
66.249.72.184 66.249.74.95 66.249.75.157 66.249.75.30
66.249.74.91 66.249.75.155 66.249.79.73 66.249.79.239
66.249.79.223 66.249.80.43 66.249.80.47 66.249.79.29