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 of America (the)

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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 132.197.133.19
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50722
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;132.197.133.19.			IN	A

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

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 13:48:51 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 19.133.197.132.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
server can't find 132.197.133.19.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
139.59.254.74 attackbotsspam
POST /xmlrpc.php.  Part of botnet attack -- 34 POST requests from 19 different IP addresses.
2019-12-27 00:20:59
46.119.180.141 attackbotsspam
/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-27 00:02:56
160.153.153.29 attackspambots
POST /xmlrpc.php.  Part of botnet attack -- 34 POST requests from 19 different IP addresses.
2019-12-27 00:16:39
39.50.89.174 attack
GET /wp-login.php
2019-12-27 00:07:08
159.89.16.69 attack
GET /site/wp-login.php
2019-12-27 00:17:21
138.197.146.132 attackbots
GET /wp-login.php
2019-12-27 00:21:34
64.202.188.156 attack
GET /wp-login.php
2019-12-26 23:59:16
35.189.72.205 attackbotsspam
GET /site/wp-login.php
2019-12-27 00:10:15
64.95.98.37 attackbotsspam
firewall-block, port(s): 5060/udp
2019-12-27 00:37:02
172.105.71.4 attackspam
GET /index.php
2019-12-27 00:13:03
139.59.136.84 attackbotsspam
GET /web/wp-login.php
2019-12-27 00:21:17
46.191.226.95 attackspam
GET /wp-login.php
2019-12-27 00:02:35
134.209.39.98 attack
GET /web/wp-login.php
2019-12-27 00:22:21
39.99.132.185 attack
The IP has triggered Cloudflare WAF. CF-Ray: 54b3a5d83ad0e805 | WAF_Rule_ID: a75424b44a1e4f27881d03344a122815 | WAF_Kind: firewall | CF_Action: drop | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: HEAD | Host: blog.skk.moe | User-Agent:  | CF_DC: LAX. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-27 00:06:26
104.131.19.173 attackbotsspam
GET /wp-login.php
2019-12-27 00:30:52

Recently Reported IPs

55.78.209.150 168.123.120.189 52.179.4.86 224.250.120.97
225.195.180.91 161.86.195.191 230.162.33.242 120.112.167.161
91.254.222.138 83.154.244.15 59.231.117.204 122.127.82.120
216.162.237.80 181.235.72.4 28.250.9.26 16.129.47.38
93.167.35.84 22.41.133.186 65.120.189.1 90.172.113.101