City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
IP | Type | Details | Datetime |
---|---|---|---|
66.249.66.82 | spambotsattack | [N10.H2.VM2] Port Scanner Detected Blocked by UFW |
2023-02-18 16:13:23 |
66.249.66.82 | attackspam | Automatic report - Banned IP Access |
2020-09-20 02:00:46 |
66.249.66.81 | attackbotsspam | 66.249.66.81 - - [19/Sep/2020:08:10:35 +0200] "GET /info/wp-login.php HTTP/1.1" 404 4264 "-" "Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.110 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" |
2020-09-19 23:59:44 |
66.249.66.157 | attackspam | Automatic report - Banned IP Access |
2020-09-19 22:53:34 |
66.249.66.82 | attack | Automatic report - Banned IP Access |
2020-09-19 17:53:19 |
66.249.66.81 | attackbotsspam | 66.249.66.81 - - [19/Sep/2020:08:10:35 +0200] "GET /info/wp-login.php HTTP/1.1" 404 4264 "-" "Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.110 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" |
2020-09-19 15:48:57 |
66.249.66.157 | attack | Automatic report - Banned IP Access |
2020-09-19 14:43:46 |
66.249.66.81 | attackspambots | Automatic report - Banned IP Access |
2020-09-19 07:23:27 |
66.249.66.157 | attack | Automatic report - Banned IP Access |
2020-09-19 06:20:01 |
66.249.66.219 | attackspam | Automatic report - Banned IP Access |
2020-09-08 03:08:18 |
66.249.66.219 | attackspam | Automatic report - Banned IP Access |
2020-09-07 18:37:09 |
66.249.66.207 | attack | Automatic report - Banned IP Access |
2020-09-01 07:45:23 |
66.249.66.138 | attackbots | Automatic report - Banned IP Access |
2020-08-31 16:43:42 |
66.249.66.27 | attackspambots | Automatic report - Banned IP Access |
2020-08-27 12:27:16 |
66.249.66.220 | attackspambots | Automatic report - Banned IP Access |
2020-08-27 03:06:14 |
b'#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2025, American Registry for Internet Numbers, Ltd.
#
NetRange: 66.249.64.0 - 66.249.95.255
CIDR: 66.249.64.0/19
NetName: GOOGLE
NetHandle: NET-66-249-64-0-1
Parent: NET66 (NET-66-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Google LLC (GOGL)
RegDate: 2004-03-05
Updated: 2012-02-24
Ref: https://rdap.arin.net/registry/ip/66.249.64.0
OrgName: Google LLC
OrgId: GOGL
Address: 1600 Amphitheatre Parkway
City: Mountain View
StateProv: CA
PostalCode: 94043
Country: US
RegDate: 2000-03-30
Updated: 2019-10-31
Comment: Please note that the recommended way to file abuse complaints are located in the following links.
Comment:
Comment: To report abuse and illegal activity: https://www.google.com/contact/
Comment:
Comment: For legal requests: http://support.google.com/legal
Comment:
Comment: Regards,
Comment: The Google Team
Ref: https://rdap.arin.net/registry/entity/GOGL
OrgAbuseHandle: ABUSE5250-ARIN
OrgAbuseName: Abuse
OrgAbusePhone: +1-650-253-0000
OrgAbuseEmail: network-abuse@google.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE5250-ARIN
OrgTechHandle: ZG39-ARIN
OrgTechName: Google LLC
OrgTechPhone: +1-650-253-0000
OrgTechEmail: arin-contact@google.com
OrgTechRef: https://rdap.arin.net/registry/entity/ZG39-ARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2025, American Registry for Internet Numbers, Ltd.
#'
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 66.249.66.12
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 60175
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;66.249.66.12. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025101100 1800 900 604800 86400
;; Query time: 87 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Oct 11 23:31:24 CST 2025
;; MSG SIZE rcvd: 105
12.66.249.66.in-addr.arpa domain name pointer crawl-66-249-66-12.googlebot.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
12.66.249.66.in-addr.arpa name = crawl-66-249-66-12.googlebot.com.
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
92.63.194.59 | attack | IP attempted unauthorised action |
2020-04-20 12:48:41 |
68.183.110.49 | attackbots | $f2bV_matches |
2020-04-20 13:04:14 |
125.69.68.125 | attackspam | Apr 20 05:51:07 ns392434 sshd[27874]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.69.68.125 user=root Apr 20 05:51:10 ns392434 sshd[27874]: Failed password for root from 125.69.68.125 port 7296 ssh2 Apr 20 05:59:09 ns392434 sshd[28208]: Invalid user ap from 125.69.68.125 port 63074 Apr 20 05:59:09 ns392434 sshd[28208]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.69.68.125 Apr 20 05:59:09 ns392434 sshd[28208]: Invalid user ap from 125.69.68.125 port 63074 Apr 20 05:59:12 ns392434 sshd[28208]: Failed password for invalid user ap from 125.69.68.125 port 63074 ssh2 Apr 20 06:04:29 ns392434 sshd[28351]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.69.68.125 user=root Apr 20 06:04:31 ns392434 sshd[28351]: Failed password for root from 125.69.68.125 port 34336 ssh2 Apr 20 06:09:00 ns392434 sshd[28578]: Invalid user tester from 125.69.68.125 port 37417 |
2020-04-20 12:47:14 |
185.10.68.30 | attackbots | Apr2005:57:48server2kernel:Firewall:\*TCP_INBlocked\*IN=eth0OUT=MAC=00:16:3e:3f:7a:43:52:54:00:a2:7f:43:08:00SRC=185.10.68.30DST=136.243.224.53LEN=40TOS=0x00PREC=0x00TTL=246ID=64789PROTO=TCPSPT=59457DPT=8192WINDOW=1024RES=0x00SYNURGP=0Apr2005:57:52server2kernel:Firewall:\*TCP_INBlocked\*IN=eth0OUT=MAC=00:16:3e:3f:7a:43:52:54:00:a2:7f:43:08:00SRC=185.10.68.30DST=136.243.224.55LEN=40TOS=0x00PREC=0x00TTL=246ID=19126PROTO=TCPSPT=59457DPT=8122WINDOW=1024RES=0x00SYNURGP=0Apr2005:57:57server2kernel:Firewall:\*TCP_INBlocked\*IN=eth0OUT=MAC=00:16:3e:3f:7a:43:52:54:00:a2:7f:43:08:00SRC=185.10.68.30DST=136.243.224.53LEN=40TOS=0x00PREC=0x00TTL=246ID=64789PROTO=TCPSPT=59457DPT=8192WINDOW=1024RES=0x00SYNURGP=0Apr2005:58:02server2kernel:Firewall:\*TCP_INBlocked\*IN=eth0OUT=MAC=00:16:3e:3f:7a:43:52:54:00:a2:7f:43:08:00SRC=185.10.68.30DST=136.243.224.55LEN=40TOS=0x00PREC=0x00TTL=246ID=19126PROTO=TCPSPT=59457DPT=8122WINDOW=1024RES=0x00SYNURGP=0Apr2005:58:07server2kernel:Firewall:\*TCP_INBlocked\*IN=eth0OUT=MAC=00:16:3e:3f:7a:4 |
2020-04-20 12:49:01 |
103.69.71.60 | attackbots | Apr 20 06:05:30 h2022099 sshd[1171]: Invalid user qt from 103.69.71.60 Apr 20 06:05:30 h2022099 sshd[1171]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.69.71.60 Apr 20 06:05:31 h2022099 sshd[1171]: Failed password for invalid user qt from 103.69.71.60 port 37672 ssh2 Apr 20 06:05:32 h2022099 sshd[1171]: Received disconnect from 103.69.71.60: 11: Bye Bye [preauth] Apr 20 06:13:44 h2022099 sshd[2166]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.69.71.60 user=r.r Apr 20 06:13:45 h2022099 sshd[2166]: Failed password for r.r from 103.69.71.60 port 43628 ssh2 Apr 20 06:13:45 h2022099 sshd[2166]: Received disconnect from 103.69.71.60: 11: Bye Bye [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=103.69.71.60 |
2020-04-20 13:28:18 |
101.187.123.101 | attack | " " |
2020-04-20 13:25:03 |
94.191.124.57 | attackbotsspam | Unauthorised connection attempt detected at AUO NODE 1. System is sshd. Protected by AUO Stack Web Application Firewall (WAF) |
2020-04-20 13:13:46 |
93.118.39.1 | attack | Unauthorized connection attempt detected from IP address 93.118.39.1 to port 80 |
2020-04-20 13:22:15 |
80.82.64.73 | attackbotsspam | 04/20/2020-01:02:00.621859 80.82.64.73 Protocol: 6 ET SCAN NMAP -sS window 1024 |
2020-04-20 13:15:14 |
112.85.42.194 | attack | Apr 20 06:55:25 ift sshd\[39265\]: Failed password for root from 112.85.42.194 port 37585 ssh2Apr 20 06:56:27 ift sshd\[39430\]: Failed password for root from 112.85.42.194 port 29062 ssh2Apr 20 06:56:30 ift sshd\[39430\]: Failed password for root from 112.85.42.194 port 29062 ssh2Apr 20 06:57:36 ift sshd\[39465\]: Failed password for root from 112.85.42.194 port 38411 ssh2Apr 20 06:58:40 ift sshd\[39551\]: Failed password for root from 112.85.42.194 port 31254 ssh2 ... |
2020-04-20 13:24:25 |
203.195.200.76 | attack | /dev/license.txt |
2020-04-20 12:58:12 |
45.55.231.94 | attack | Apr 20 04:41:53 ws26vmsma01 sshd[54369]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.231.94 Apr 20 04:41:55 ws26vmsma01 sshd[54369]: Failed password for invalid user mx from 45.55.231.94 port 50272 ssh2 ... |
2020-04-20 12:51:17 |
92.63.194.32 | attackspambots | IP attempted unauthorised action |
2020-04-20 12:56:49 |
218.92.139.151 | attackbotsspam | prod6 ... |
2020-04-20 13:18:32 |
170.254.195.104 | attackspam | Apr 20 01:08:37 firewall sshd[12823]: Invalid user vv from 170.254.195.104 Apr 20 01:08:38 firewall sshd[12823]: Failed password for invalid user vv from 170.254.195.104 port 42118 ssh2 Apr 20 01:12:42 firewall sshd[13064]: Invalid user vv from 170.254.195.104 ... |
2020-04-20 12:54:24 |