City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.196.22.244
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64046
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.196.22.244. IN A
;; AUTHORITY SECTION:
. 568 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021700 1800 900 604800 86400
;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 16:14:32 CST 2022
;; MSG SIZE rcvd: 107
244.22.196.104.in-addr.arpa domain name pointer 244.22.196.104.bc.googleusercontent.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
244.22.196.104.in-addr.arpa name = 244.22.196.104.bc.googleusercontent.com.
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
83.219.134.221 | attackbotsspam | Unauthorized connection attempt detected from IP address 83.219.134.221 to port 80 [J] |
2020-01-27 01:38:41 |
114.37.79.33 | attack | Unauthorized connection attempt detected from IP address 114.37.79.33 to port 23 [J] |
2020-01-27 00:48:35 |
42.115.98.210 | attackspambots | Unauthorized connection attempt detected from IP address 42.115.98.210 to port 80 [J] |
2020-01-27 00:52:46 |
112.255.41.125 | attackbots | Unauthorized connection attempt detected from IP address 112.255.41.125 to port 23 [J] |
2020-01-27 01:34:19 |
109.229.29.99 | attack | Unauthorized connection attempt detected from IP address 109.229.29.99 to port 8080 [J] |
2020-01-27 01:35:36 |
185.37.59.132 | attack | Unauthorized connection attempt detected from IP address 185.37.59.132 to port 80 [J] |
2020-01-27 01:00:07 |
180.103.218.201 | attackspam | Unauthorized connection attempt detected from IP address 180.103.218.201 to port 81 [T] |
2020-01-27 01:29:05 |
2.133.81.180 | attack | Unauthorized connection attempt detected from IP address 2.133.81.180 to port 23 [J] |
2020-01-27 00:56:34 |
186.149.46.4 | attack | Unauthorized connection attempt detected from IP address 186.149.46.4 to port 2220 [J] |
2020-01-27 00:59:43 |
148.3.67.180 | attackbots | Unauthorized connection attempt detected from IP address 148.3.67.180 to port 23 [J] |
2020-01-27 00:43:43 |
76.171.161.240 | attack | Unauthorized connection attempt detected from IP address 76.171.161.240 to port 5555 [J] |
2020-01-27 01:39:48 |
51.68.44.13 | attackspambots | Unauthorized connection attempt detected from IP address 51.68.44.13 to port 2220 [J] |
2020-01-27 01:18:13 |
118.165.121.227 | attackspambots | Unauthorized connection attempt detected from IP address 118.165.121.227 to port 23 [J] |
2020-01-27 00:46:27 |
2.187.18.227 | attackbotsspam | Unauthorized connection attempt detected from IP address 2.187.18.227 to port 80 [J] |
2020-01-27 01:21:23 |
36.32.3.118 | attack | The IP has triggered Cloudflare WAF. CF-Ray: 55ac73ecedcfed87 | WAF_Rule_ID: a75424b44a1e4f27881d03344a122815 | WAF_Kind: firewall | CF_Action: drop | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: d.skk.moe | User-Agent: Mozilla/5.0101097241 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36 | CF_DC: SJC. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB). |
2020-01-27 00:55:47 |