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
125.164.248.16 attackbotsspam
1582753694 - 02/26/2020 22:48:14 Host: 125.164.248.16/125.164.248.16 Port: 445 TCP Blocked
2020-02-27 07:39:01
125.164.248.38 attack
20/2/5@23:53:57: FAIL: Alarm-Network address from=125.164.248.38
20/2/5@23:53:57: FAIL: Alarm-Network address from=125.164.248.38
...
2020-02-06 17:59:34
125.164.248.69 attackspam
port scan and connect, tcp 23 (telnet)
2020-01-02 14:02:51
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 125.164.248.204
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20618
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;125.164.248.204.		IN	A

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

;; Query time: 55 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 02:55:02 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 204.248.164.125.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 204.248.164.125.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
46.217.237.35 attackbotsspam
Unauthorized connection attempt detected from IP address 46.217.237.35 to port 80
2020-05-30 01:43:48
220.122.126.184 attackbots
Unauthorized connection attempt detected from IP address 220.122.126.184 to port 23
2020-05-30 01:48:06
181.197.51.137 attackspambots
Unauthorized connection attempt detected from IP address 181.197.51.137 to port 5555
2020-05-30 02:00:45
187.94.104.154 attackspam
Unauthorized connection attempt detected from IP address 187.94.104.154 to port 445
2020-05-30 01:57:21
58.65.159.196 attackbots
Unauthorized connection attempt detected from IP address 58.65.159.196 to port 445
2020-05-30 01:41:19
191.254.44.247 attackbotsspam
Unauthorized connection attempt detected from IP address 191.254.44.247 to port 8080
2020-05-30 01:54:36
113.245.78.227 attackbotsspam
Port Scan
2020-05-30 01:26:46
77.42.123.3 attack
Unauthorized connection attempt detected from IP address 77.42.123.3 to port 8080
2020-05-30 01:37:54
178.210.244.250 attack
Unauthorized connection attempt detected from IP address 178.210.244.250 to port 23
2020-05-30 02:02:15
81.246.218.220 attack
Unauthorized connection attempt detected from IP address 81.246.218.220 to port 22
2020-05-30 01:35:52
115.219.198.72 attackspambots
Port Scan
2020-05-30 01:23:42
52.232.188.182 attackspam
Unauthorized connection attempt detected from IP address 52.232.188.182 to port 8080
2020-05-30 01:41:37
117.221.16.226 attackbots
Unauthorized connection attempt detected from IP address 117.221.16.226 to port 445
2020-05-30 01:22:00
106.13.78.121 attackbots
Port Scan
2020-05-30 01:28:26
179.179.218.75 attackbotsspam
Automatic report - Port Scan Attack
2020-05-30 02:01:15

Recently Reported IPs

125.164.248.201 125.164.248.221 125.164.249.133 125.164.248.174
125.164.249.193 125.164.249.209 117.91.131.48 125.164.249.222
125.164.249.65 117.91.131.5 117.91.131.51 117.91.131.54
117.91.131.56 117.91.131.59 117.91.131.62 73.185.247.114
125.164.33.93 125.164.33.139 117.91.131.67 125.164.34.144