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: Korea (the Republic of)

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

;; QUESTION SECTION:
;222.117.180.125.		IN	A

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

;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 14 17:44:34 CST 2025
;; MSG SIZE  rcvd: 108
Host info
Host 125.180.117.222.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 125.180.117.222.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
203.195.152.247 attack
$f2bV_matches
2020-01-08 21:23:31
197.210.8.18 attackspam
20/1/8@08:07:10: FAIL: Alarm-Network address from=197.210.8.18
20/1/8@08:07:10: FAIL: Alarm-Network address from=197.210.8.18
...
2020-01-08 21:18:45
106.13.124.124 attack
Unauthorized connection attempt detected from IP address 106.13.124.124 to port 2220 [J]
2020-01-08 20:52:11
45.136.108.117 attackbotsspam
Jan  8 14:07:27 debian-2gb-nbg1-2 kernel: \[748162.883390\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=45.136.108.117 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=33091 PROTO=TCP SPT=41027 DPT=9229 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-08 21:09:21
134.209.102.147 attackspam
134.209.102.147 - - [08/Jan/2020:14:06:44 +0100] "POST /wp-login.php HTTP/1.1" 200 3121 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
134.209.102.147 - - [08/Jan/2020:14:06:45 +0100] "POST /wp-login.php HTTP/1.1" 200 3100 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-01-08 21:33:46
49.88.112.116 attackbots
SSH bruteforce (Triggered fail2ban)
2020-01-08 21:25:45
171.253.58.199 attackspambots
Telnet Server BruteForce Attack
2020-01-08 20:50:43
52.187.106.61 attackbots
SSH bruteforce (Triggered fail2ban)
2020-01-08 21:08:12
223.71.167.164 attackspambots
08.01.2020 13:16:09 Connection to port 12000 blocked by firewall
2020-01-08 21:07:37
113.173.10.89 attack
Unauthorized IMAP connection attempt
2020-01-08 21:17:31
180.97.80.12 attack
Unauthorized connection attempt detected from IP address 180.97.80.12 to port 2220 [J]
2020-01-08 21:02:35
222.186.31.166 attack
Jan  8 08:16:11 TORMINT sshd\[31605\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.166  user=root
Jan  8 08:16:13 TORMINT sshd\[31605\]: Failed password for root from 222.186.31.166 port 19284 ssh2
Jan  8 08:16:16 TORMINT sshd\[31605\]: Failed password for root from 222.186.31.166 port 19284 ssh2
...
2020-01-08 21:24:15
114.141.191.238 attackbots
$f2bV_matches
2020-01-08 21:06:38
45.82.152.250 attack
0,17-03/33 [bc01/m26] PostRequest-Spammer scoring: maputo01_x2b
2020-01-08 21:23:57
180.113.36.226 attackbots
Port scan on 1 port(s): 21
2020-01-08 21:05:50

Recently Reported IPs

171.195.117.207 241.211.20.126 66.40.136.216 80.157.206.242
91.33.25.47 209.106.51.185 19.130.113.160 142.4.169.178
40.189.236.85 26.79.248.125 53.165.57.64 226.120.237.184
129.129.197.47 218.214.235.17 208.92.44.144 14.107.68.37
227.220.240.1 108.144.167.209 164.65.241.6 206.237.167.83