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

;; QUESTION SECTION:
;219.40.139.42.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 15 16:26:13 CST 2025
;; MSG SIZE  rcvd: 106
Host info
42.139.40.219.in-addr.arpa domain name pointer softbank219040139042.bbtec.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
42.139.40.219.in-addr.arpa	name = softbank219040139042.bbtec.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
45.82.153.133 attackbotsspam
Nov 18 06:35:09 heicom postfix/smtpd\[3911\]: warning: unknown\[45.82.153.133\]: SASL LOGIN authentication failed: authentication failure
Nov 18 06:35:15 heicom postfix/smtpd\[4827\]: warning: unknown\[45.82.153.133\]: SASL LOGIN authentication failed: authentication failure
Nov 18 06:57:38 heicom postfix/smtpd\[4827\]: warning: unknown\[45.82.153.133\]: SASL LOGIN authentication failed: authentication failure
Nov 18 06:57:45 heicom postfix/smtpd\[3911\]: warning: unknown\[45.82.153.133\]: SASL LOGIN authentication failed: authentication failure
Nov 18 07:25:01 heicom postfix/smtpd\[6592\]: warning: unknown\[45.82.153.133\]: SASL LOGIN authentication failed: authentication failure
...
2019-11-18 15:27:02
112.218.169.189 attackbots
Autoban   112.218.169.189 AUTH/CONNECT
2019-11-18 15:56:24
1.58.113.162 attackbots
Fail2Ban - FTP Abuse Attempt
2019-11-18 15:38:46
63.88.23.218 attackspambots
63.88.23.218 was recorded 22 times by 8 hosts attempting to connect to the following ports: 80. Incident counter (4h, 24h, all-time): 22, 58, 204
2019-11-18 15:22:02
218.92.0.186 attackspam
SSHScan
2019-11-18 15:40:27
112.145.115.49 attack
Autoban   112.145.115.49 AUTH/CONNECT
2019-11-18 15:59:56
112.45.122.7 attackspam
Autoban   112.45.122.7 AUTH/CONNECT
2019-11-18 15:54:09
111.197.64.32 attackbotsspam
Fail2Ban - FTP Abuse Attempt
2019-11-18 15:32:04
113.88.166.121 attackspam
Brute force attempt
2019-11-18 15:44:55
112.45.122.9 attackbotsspam
$f2bV_matches
2019-11-18 15:52:15
121.142.165.111 attack
SSH Bruteforce
2019-11-18 15:30:34
150.136.239.220 attackspambots
150.136.239.220 was recorded 11 times by 10 hosts attempting to connect to the following ports: 4243,2376,2375. Incident counter (4h, 24h, all-time): 11, 57, 177
2019-11-18 15:23:27
112.216.51.122 attack
Nov 18 08:32:25 MK-Soft-VM4 sshd[30029]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.216.51.122 
Nov 18 08:32:27 MK-Soft-VM4 sshd[30029]: Failed password for invalid user prince from 112.216.51.122 port 54285 ssh2
...
2019-11-18 15:45:17
113.92.223.152 attack
Unauthorised access (Nov 18) SRC=113.92.223.152 LEN=52 TTL=117 ID=542 DF TCP DPT=445 WINDOW=8192 SYN
2019-11-18 15:44:38
112.133.248.120 attackspam
Autoban   112.133.248.120 AUTH/CONNECT
2019-11-18 16:02:10

Recently Reported IPs

41.200.152.176 19.2.200.37 120.42.75.135 217.0.13.104
149.200.221.13 205.67.47.128 73.199.171.32 170.134.249.94
172.128.175.166 16.136.199.170 232.61.112.237 64.172.122.200
138.115.255.249 69.198.14.41 134.115.209.243 204.11.168.14
173.48.75.185 31.58.16.141 235.132.142.94 78.175.160.20