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: Japan

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
202.254.234.82 attackspambots
LGS,WP GET /wp-login.php
2020-02-25 17:39:24
202.254.234.35 attackspambots
Attempted WordPress login: "GET /cms/wp-login.php"
2019-09-26 21:32:22
202.254.234.103 attack
Scanning and Vuln Attempts
2019-09-25 14:48:48
202.254.234.142 attackbotsspam
Scanning and Vuln Attempts
2019-09-25 14:47:35
202.254.234.151 attack
Scanning and Vuln Attempts
2019-09-25 14:43:21
Whois info:
[ JPNIC database provides information regarding IP address and ASN. Its use   ]
[ is restricted to network administration purposes. For further information,  ]
[ use 'whois -h whois.nic.ad.jp help'. To only display English output,        ]
[ add '/e' at the end of command, e.g. 'whois -h whois.nic.ad.jp xxx/e'.      ]

Network Information:            
a. [Network Number]             202.254.234.0/24
b. [Network Name]               XSERVER16
g. [Organization]               XServer Cloud Inc.
m. [Administrative Contact]     JT25220JP
n. [Technical Contact]          JT25220JP
o. [Abuse]                      abuse@xserver.co.jp
p. [Nameserver]                 ns1.xserver.jp
p. [Nameserver]                 ns2.xserver.jp
p. [Nameserver]                 ns3.xserver.jp
p. [Nameserver]                 ns4.xserver.jp
p. [Nameserver]                 ns5.xserver.jp
[Assigned Date]                 2017/07/05
[Return Date]                   
[Last Update]                   2026/09/14 17:35:04(JST)
                                
Less Specific Info.
----------
XServer Networks Inc.
                     [Allocation]                             202.254.232.0/21

More Specific Info.
----------
No match!!
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 202.254.234.5
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11580
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;202.254.234.5.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Oct 11 07:45:41 CST 2026
;; MSG SIZE  rcvd: 106
Host info
5.234.254.202.in-addr.arpa domain name pointer sv3004.xserver.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
5.234.254.202.in-addr.arpa	name = sv3004.xserver.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
5.39.82.197 attackspambots
2019-11-29T15:39:20.3530081495-001 sshd\[43776\]: Failed password for invalid user bergren from 5.39.82.197 port 52280 ssh2
2019-11-29T16:41:06.8939751495-001 sshd\[46094\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns3270404.ip-5-39-82.eu  user=root
2019-11-29T16:41:08.4177681495-001 sshd\[46094\]: Failed password for root from 5.39.82.197 port 45586 ssh2
2019-11-29T16:51:00.2055361495-001 sshd\[46520\]: Invalid user webadmin from 5.39.82.197 port 51960
2019-11-29T16:51:00.2153321495-001 sshd\[46520\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns3270404.ip-5-39-82.eu
2019-11-29T16:51:02.5133051495-001 sshd\[46520\]: Failed password for invalid user webadmin from 5.39.82.197 port 51960 ssh2
...
2019-11-30 06:48:04
3.88.143.18 attack
port scan/probe/communication attempt
2019-11-30 06:50:49
212.129.145.64 attack
2019-11-29T21:45:14.347330abusebot-2.cloudsearch.cf sshd\[9751\]: Invalid user fairman from 212.129.145.64 port 45579
2019-11-30 06:32:50
157.245.239.1 attackspam
SSH login attempts with user root.
2019-11-30 06:17:14
157.97.94.1 attackbots
web Attack on Wordpress site
2019-11-30 06:17:29
152.250.9.2 attack
web Attack on Wordpress site
2019-11-30 06:17:48
78.24.217.236 attackbots
"GET /_adminer HTTP/1.1" 404
"GET /_adminer.php HTTP/1.1" 404
"GET /ad.php HTTP/1.1" 404
"GET /adm.php HTTP/1.1" 404
"GET /adminer HTTP/1.1" 404
"GET /adminer.php HTTP/1.1" 404
"GET /db.php HTTP/1.1" 404
"GET /mysql.php HTTP/1.1" 404
2019-11-30 06:50:09
141.98.81.1 attackspambots
SSH login attempts with user root.
2019-11-30 06:25:09
106.13.147.6 attack
SSH login attempts with user root.
2019-11-30 06:52:47
120.232.39.163 attackbotsspam
1433/tcp 1433/tcp 1433/tcp...
[2019-10-19/11-29]4pkt,1pt.(tcp)
2019-11-30 06:32:13
128.199.44.1 attack
SSH login attempts with user root.
2019-11-30 06:34:14
14.192.210.2 attackbotsspam
SSH login attempts with user root.
2019-11-30 06:27:27
132.232.53.4 attack
SSH login attempts with user root.
2019-11-30 06:33:10
114.118.96.2 attackbotsspam
SSH login attempts with user root.
2019-11-30 06:42:17
49.233.91.133 attackbots
Nov 29 21:44:32 server sshd\[24697\]: Invalid user floresn from 49.233.91.133
Nov 29 21:44:32 server sshd\[24697\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.91.133 
Nov 29 21:44:34 server sshd\[24697\]: Failed password for invalid user floresn from 49.233.91.133 port 45424 ssh2
Nov 29 21:57:23 server sshd\[28092\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.91.133  user=root
Nov 29 21:57:25 server sshd\[28092\]: Failed password for root from 49.233.91.133 port 33914 ssh2
...
2019-11-30 06:47:51

Recently Reported IPs

209.164.235.43 208.211.210.168 209.112.246.108 206.255.249.212
205.198.12.45 208.10.216.118 204.249.69.19 203.237.173.54
208.104.117.116 202.180.120.22 203.10.89.174 202.9.36.158
20.14.94.24 202.27.212.127 201.220.140.40 3.238.108.112
54.221.141.122 8.219.133.78 52.91.204.84 165.22.145.25