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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 220.34.172.54
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16817
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;220.34.172.54.			IN	A

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

;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 29 05:27:27 CST 2025
;; MSG SIZE  rcvd: 106
Host info
54.172.34.220.in-addr.arpa domain name pointer softbank220034172054.bbtec.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
54.172.34.220.in-addr.arpa	name = softbank220034172054.bbtec.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
103.194.107.242 attackspambots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-04-11 08:11:15
68.183.56.212 attackbotsspam
frenzy
2020-04-11 07:54:35
92.63.194.91 attackspam
Apr 11 02:11:35 vps647732 sshd[19888]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.63.194.91
Apr 11 02:11:36 vps647732 sshd[19888]: Failed password for invalid user admin from 92.63.194.91 port 34255 ssh2
...
2020-04-11 08:17:31
94.102.56.181 attack
Apr 11 01:30:50 debian-2gb-nbg1-2 kernel: \[8820456.298512\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=94.102.56.181 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=40246 PROTO=TCP SPT=49646 DPT=9337 WINDOW=1024 RES=0x00 SYN URGP=0
2020-04-11 08:13:02
92.118.37.99 attackspam
Apr 11 02:00:56 debian-2gb-nbg1-2 kernel: \[8822261.635694\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=92.118.37.99 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=11117 PROTO=TCP SPT=45456 DPT=10613 WINDOW=1024 RES=0x00 SYN URGP=0
2020-04-11 08:16:01
64.225.14.108 attackbotsspam
Invalid user saned from 64.225.14.108 port 33822
2020-04-11 07:55:29
89.144.47.247 attackbotsspam
04/10/2020-19:05:31.568150 89.144.47.247 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-04-11 08:19:19
45.143.221.60 attack
04/10/2020-16:42:23.566194 45.143.221.60 Protocol: 17 ET SCAN Sipvicious Scan
2020-04-11 07:57:50
79.124.62.66 attack
04/10/2020-19:53:51.101944 79.124.62.66 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-04-11 08:23:43
13.68.178.52 attackspambots
04/10/2020-18:18:37.197350 13.68.178.52 Protocol: 17 ET SCAN Sipvicious Scan
2020-04-11 08:02:17
122.228.120.190 attackbots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-04-11 08:09:04
36.26.78.36 attackspam
Invalid user ubuntu from 36.26.78.36 port 49914
2020-04-11 08:01:12
141.98.81.150 attackspam
ET SCAN Potential SSH Scan - port: 22 proto: TCP cat: Attempted Information Leak
2020-04-11 08:07:57
58.214.255.41 attackspambots
Unauthorized connection attempt detected from IP address 58.214.255.41 to port 4366
2020-04-11 07:56:19
92.118.160.37 attackspam
" "
2020-04-11 08:15:34

Recently Reported IPs

59.152.74.21 187.146.55.45 66.253.8.241 4.64.121.203
157.142.38.17 73.199.59.3 99.231.146.76 184.94.92.59
236.90.38.118 208.87.127.199 253.212.217.169 41.57.121.164
168.116.164.113 5.230.250.12 9.203.112.91 132.76.96.199
130.73.168.127 88.79.113.195 7.1.55.176 3.211.21.70