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: None

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
1.70.64.88 attackbotsspam
Sep  1 13:28:14 shivevps sshd[28391]: Bad protocol version identification '\024' from 1.70.64.88 port 34368
...
2020-09-02 03:23:12
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 1.70.64.134
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43046
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;1.70.64.134.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 00:00:01 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 134.64.70.1.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 134.64.70.1.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
178.54.94.14 attackspam
/2018/wp-includes/wlwmanifest.xml
/2019/wp-includes/wlwmanifest.xml
/blog/wp-includes/wlwmanifest.xml
/cms/wp-includes/wlwmanifest.xml
/media/wp-includes/wlwmanifest.xml
/news/wp-includes/wlwmanifest.xml
/shop/wp-includes/wlwmanifest.xml
/site/wp-includes/wlwmanifest.xml
/sito/wp-includes/wlwmanifest.xml
/test/wp-includes/wlwmanifest.xml
/web/wp-includes/wlwmanifest.xml
/website/wp-includes/wlwmanifest.xml
/wordpress/wp-includes/wlwmanifest.xml
/wp/wp-includes/wlwmanifest.xml
/wp1/wp-includes/wlwmanifest.xml
/wp2/wp-includes/wlwmanifest.xml
/wp-includes/wlwmanifest.xml
/xmlrpc.php?rsd
2019-12-26 23:53:06
89.7.187.108 attack
POST /xmlrpc.php.  Part of botnet attack -- 34 POST requests from 19 different IP addresses.
2019-12-26 23:56:48
118.31.67.1 attack
GET /panel/tables.php
2019-12-27 00:25:30
138.197.95.2 attackbots
GET /wp-login.php
2019-12-27 00:21:58
84.54.12.246 attackspambots
GET /wp-content/feal.php
2019-12-26 23:57:52
123.31.43.173 attackbots
GET /test/wp-login.php
2019-12-27 00:24:51
95.142.118.20 attackbotsspam
Spam via website contact form
2019-12-26 23:54:08
159.65.65.204 attackspambots
GET /installer.php
GET /installer-backup.php
GET /replace.php
GET /unzip.php
GET /unzipper.php
GET /urlreplace.php
2019-12-27 00:19:21
107.180.120.45 attackbotsspam
POST /xmlrpc.php.  Part of botnet attack -- 34 POST requests from 19 different IP addresses.
2019-12-27 00:27:08
159.65.78.120 attackspambots
GET requests for autodiscover. and webdisk.
/vendor/phpunit/phpunit/build.xml and /vendor/phpunit/phpunit/LICENSE
2019-12-27 00:18:57
89.145.74.91 attack
GET /site/wp-login.php
2019-12-26 23:55:49
85.236.161.11 attack
POST /login/?login_only=1  Attempting to login via port 2083.  No user agent.
2019-12-26 23:57:16
109.165.50.170 attackspambots
GET /wp-login.php
2019-12-27 00:26:36
154.209.253.149 attackbots
The IP has triggered Cloudflare WAF. CF-Ray: 54aca0fcba5ca29a | WAF_Rule_ID: 53b8357af6d244d3a132bcf913c3a388 | WAF_Kind: firewall | CF_Action: drop | Country: HK | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: skk.moe | User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0 | CF_DC: HKG. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-27 00:19:48
178.128.220.224 attackbotsspam
GET /wp-json/wp/v2/users/
2019-12-26 23:52:17

Recently Reported IPs

1.70.64.133 1.70.64.136 1.70.64.138 1.70.64.140
1.70.64.142 1.70.64.144 1.70.64.146 1.70.64.149
1.70.64.15 1.70.64.151 1.70.64.152 1.70.64.154
1.70.64.156 1.70.64.158 1.70.64.160 200.254.239.0
1.70.64.162 1.70.64.165 1.70.64.167 1.70.64.168