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

;; QUESTION SECTION:
;253.5.66.10.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 15:55:18 CST 2025
;; MSG SIZE  rcvd: 104
Host info
Host 10.66.5.253.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 10.66.5.253.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
80.76.244.151 attack
Jan 31 10:28:31 firewall sshd[13223]: Invalid user sama from 80.76.244.151
Jan 31 10:28:33 firewall sshd[13223]: Failed password for invalid user sama from 80.76.244.151 port 32869 ssh2
Jan 31 10:31:24 firewall sshd[13302]: Invalid user atma from 80.76.244.151
...
2020-01-31 22:24:55
167.114.152.139 attackbots
Unauthorized connection attempt detected from IP address 167.114.152.139 to port 2220 [J]
2020-01-31 22:26:08
124.235.138.104 attackspam
124.235.138.104 - - \[31/Jan/2020:10:43:42 +0200\] "GET http://www.epochtimes.com/ HTTP/1.1" 200 381 "-" "Mozilla/5.0 \(Windows NT 10.0\; WOW64\) AppleWebKit/537.36 \(KHTML, like Gecko\) Chrome/45.0.2454.101 Safari/537.36"
2020-01-31 22:44:42
51.75.24.200 attackspam
SSH Brute Force, server-1 sshd[22493]: Failed password for invalid user mokpongy from 51.75.24.200 port 49940 ssh2
2020-01-31 22:38:20
58.48.131.1 attackbotsspam
Unauthorized connection attempt detected from IP address 58.48.131.1 to port 6666 [J]
2020-01-31 22:43:58
79.173.157.26 attackbots
TCP Port Scanning
2020-01-31 22:31:52
192.99.15.132 attackbotsspam
$f2bV_matches
2020-01-31 22:28:52
5.9.156.20 attackbotsspam
20 attempts against mh-misbehave-ban on comet
2020-01-31 22:12:56
141.98.80.173 attack
Too many connections or unauthorized access detected from Yankee banned ip
2020-01-31 22:44:21
185.216.140.252 attack
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2020-01-31 22:28:00
128.72.185.93 attackspambots
TCP Port Scanning
2020-01-31 22:21:28
123.206.18.49 attackspam
Unauthorized connection attempt detected from IP address 123.206.18.49 to port 2220 [J]
2020-01-31 22:25:44
93.174.93.163 attackbots
Jan 31 15:11:26 debian-2gb-nbg1-2 kernel: \[2739145.228898\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=93.174.93.163 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=32545 PROTO=TCP SPT=46126 DPT=14211 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-31 22:22:51
103.16.27.81 attackspambots
TCP Port Scanning
2020-01-31 22:47:47
222.186.31.166 attackbotsspam
Unauthorized connection attempt detected from IP address 222.186.31.166 to port 22 [T]
2020-01-31 22:34:52

Recently Reported IPs

197.149.154.141 85.222.148.6 215.174.171.38 131.26.161.92
49.107.230.26 56.92.190.189 48.39.201.80 57.124.102.52
8.223.161.193 80.92.202.127 242.243.79.8 126.110.175.216
83.52.99.156 144.67.183.250 138.220.104.237 24.167.159.191
55.162.78.204 42.148.159.99 198.75.217.202 253.42.73.29