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

;; QUESTION SECTION:
;220.48.130.139.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 17 09:47:07 CST 2025
;; MSG SIZE  rcvd: 107
Host info
139.130.48.220.in-addr.arpa domain name pointer softbank220048130139.bbtec.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
139.130.48.220.in-addr.arpa	name = softbank220048130139.bbtec.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
140.143.222.95 attack
Jan  3 00:22:35 v22018076590370373 sshd[15801]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.222.95 
...
2020-02-02 05:42:19
183.88.226.100 attackbotsspam
Honeypot attack, port: 445, PTR: mx-ll-183.88.226-100.dynamic.3bb.co.th.
2020-02-02 05:40:54
222.186.42.136 attackspambots
Fail2Ban Ban Triggered
2020-02-02 06:15:22
45.224.105.213 attack
(imapd) Failed IMAP login from 45.224.105.213 (AR/Argentina/-): 1 in the last 3600 secs
2020-02-02 06:17:23
45.134.179.15 attackbots
02/01/2020-16:59:47.008194 45.134.179.15 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-02-02 06:13:45
1.53.223.20 attackbotsspam
firewall-block, port(s): 81/tcp
2020-02-02 06:03:16
218.92.0.168 attackbots
2020-2-1 10:59:43 PM: failed ssh attempt
2020-02-02 06:16:05
176.59.129.138 attackspam
Unauthorized connection attempt from IP address 176.59.129.138 on Port 445(SMB)
2020-02-02 05:49:54
73.93.102.54 attackbots
Unauthorized connection attempt detected from IP address 73.93.102.54 to port 22
2020-02-02 06:08:27
180.76.183.99 attack
Feb  1 22:59:49 ns381471 sshd[24302]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.183.99
Feb  1 22:59:50 ns381471 sshd[24302]: Failed password for invalid user git_user from 180.76.183.99 port 34928 ssh2
2020-02-02 06:10:59
140.143.200.251 attack
Automatic report - Banned IP Access
2020-02-02 05:47:48
80.66.81.143 attackspam
f2b trigger Multiple SASL failures
2020-02-02 05:40:00
158.69.220.70 attackbotsspam
Feb  2 00:39:33 server sshd\[11807\]: Invalid user ansible from 158.69.220.70
Feb  2 00:39:33 server sshd\[11807\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=70.ip-158-69-220.net 
Feb  2 00:39:35 server sshd\[11807\]: Failed password for invalid user ansible from 158.69.220.70 port 59120 ssh2
Feb  2 00:50:11 server sshd\[14620\]: Invalid user user from 158.69.220.70
Feb  2 00:50:11 server sshd\[14620\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=70.ip-158-69-220.net 
...
2020-02-02 05:53:01
111.254.40.136 attackspam
Honeypot attack, port: 445, PTR: 111-254-40-136.dynamic-ip.hinet.net.
2020-02-02 05:48:38
51.75.160.215 attackbotsspam
Unauthorized connection attempt detected from IP address 51.75.160.215 to port 2220 [J]
2020-02-02 06:07:20

Recently Reported IPs

20.189.110.106 211.83.252.206 116.63.43.233 247.197.205.41
87.62.134.229 162.162.58.12 108.230.65.181 83.185.246.240
99.231.5.191 126.162.121.11 168.49.138.137 213.110.184.119
211.144.197.168 144.168.133.145 212.152.94.114 69.21.162.139
36.222.48.50 120.195.56.4 131.54.21.218 243.227.59.233