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: IANA Special-Purpose Address

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 <<>> 252.213.149.36
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 29527
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;252.213.149.36.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 27 07:58:50 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 36.149.213.252.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 36.149.213.252.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
85.204.129.123 attackbots
Attempt to attack host OS, exploiting network vulnerabilities, on 01-10-2019 22:00:22.
2019-10-02 09:28:42
128.14.152.45 attack
3389BruteforceFW22
2019-10-02 12:08:35
113.185.74.1 spamattackproxy
Toi không thích id này tiêu hao nhiều dữ liệu wed nặng máy
2019-10-02 10:56:33
95.77.98.190 attack
firewall-block, port(s): 85/tcp
2019-10-02 09:21:49
77.240.152.18 attackspambots
IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/77.240.152.18/ 
 RU - 1H : (749)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : RU 
 NAME ASN : ASN42245 
 
 IP : 77.240.152.18 
 
 CIDR : 77.240.144.0/20 
 
 PREFIX COUNT : 1 
 
 UNIQUE IP COUNT : 4096 
 
 
 WYKRYTE ATAKI Z ASN42245 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-10-02 05:55:10 
 
 INFO : Port MAX SCAN Scan Detected and Blocked by ADMIN  - data recovery
2019-10-02 12:02:29
223.100.164.221 attackbotsspam
2019-10-01T22:52:22.596107shield sshd\[3233\]: Invalid user taurai from 223.100.164.221 port 57502
2019-10-01T22:52:22.600936shield sshd\[3233\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.100.164.221
2019-10-01T22:52:24.569337shield sshd\[3233\]: Failed password for invalid user taurai from 223.100.164.221 port 57502 ssh2
2019-10-01T22:55:35.741492shield sshd\[3802\]: Invalid user mongodb from 223.100.164.221 port 52655
2019-10-01T22:55:35.744705shield sshd\[3802\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.100.164.221
2019-10-02 09:12:44
189.86.169.78 attack
Unauthorized connection attempt from IP address 189.86.169.78 on Port 445(SMB)
2019-10-02 09:28:59
159.203.201.201 attackbotsspam
scan z
2019-10-02 09:23:38
196.218.38.151 attack
Oct  1 23:50:18 f201 sshd[19316]: reveeclipse mapping checking getaddrinfo for host-196.218.38.151-static.tedata.net [196.218.38.151] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct  1 23:50:19 f201 sshd[19316]: Connection closed by 196.218.38.151 [preauth]
Oct  2 02:59:57 f201 sshd[19359]: reveeclipse mapping checking getaddrinfo for host-196.218.38.151-static.tedata.net [196.218.38.151] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct  2 02:59:58 f201 sshd[19359]: Connection closed by 196.218.38.151 [preauth]
Oct  2 04:55:36 f201 sshd[16918]: reveeclipse mapping checking getaddrinfo for host-196.218.38.151-static.tedata.net [196.218.38.151] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct  2 04:55:36 f201 sshd[16918]: Connection closed by 196.218.38.151 [preauth]
Oct  2 05:47:41 f201 sshd[30223]: reveeclipse mapping checking getaddrinfo for host-196.218.38.151-static.tedata.net [196.218.38.151] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct  2 05:47:41 f201 sshd[30223]: Connection closed by 196.218.3........
-------------------------------
2019-10-02 12:10:43
222.186.42.163 attackbotsspam
SSH Bruteforce
2019-10-02 09:16:40
36.67.42.83 attackbotsspam
Unauthorized connection attempt from IP address 36.67.42.83 on Port 445(SMB)
2019-10-02 09:05:03
37.187.22.227 attackspambots
2019-10-02T01:13:11.215564shield sshd\[25577\]: Invalid user dave from 37.187.22.227 port 35442
2019-10-02T01:13:11.218700shield sshd\[25577\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ks3357677.kimsufi.com
2019-10-02T01:13:13.090662shield sshd\[25577\]: Failed password for invalid user dave from 37.187.22.227 port 35442 ssh2
2019-10-02T01:17:17.395547shield sshd\[26026\]: Invalid user wwwrun from 37.187.22.227 port 47916
2019-10-02T01:17:17.400119shield sshd\[26026\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ks3357677.kimsufi.com
2019-10-02 09:24:19
5.26.250.185 attackbotsspam
Oct  2 08:16:00 webhost01 sshd[10294]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.26.250.185
Oct  2 08:16:02 webhost01 sshd[10294]: Failed password for invalid user admin from 5.26.250.185 port 50278 ssh2
...
2019-10-02 09:22:36
210.245.52.7 attackbots
Unauthorized connection attempt from IP address 210.245.52.7 on Port 445(SMB)
2019-10-02 09:33:19
103.92.25.199 attack
Oct  1 23:54:58 markkoudstaal sshd[8520]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.92.25.199
Oct  1 23:54:59 markkoudstaal sshd[8520]: Failed password for invalid user rdp from 103.92.25.199 port 32868 ssh2
Oct  1 23:59:56 markkoudstaal sshd[8931]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.92.25.199
2019-10-02 09:15:37

Recently Reported IPs

96.230.34.58 220.99.132.108 15.24.35.205 26.72.255.38
24.226.250.175 198.84.16.214 224.223.54.188 163.7.252.233
35.239.173.71 72.238.35.232 108.68.41.40 13.106.80.39
226.224.124.227 153.209.222.232 166.84.40.143 62.156.59.192
128.228.70.240 226.131.208.43 36.189.232.19 140.14.7.130