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: Hong Kong

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

;; QUESTION SECTION:
;139.5.202.106.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 12:04:17 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 106.202.5.139.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 106.202.5.139.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
178.62.234.124 attack
370. On Jun 9 2020 experienced a Brute Force SSH login attempt -> 26 unique times by 178.62.234.124.
2020-06-10 07:51:23
61.155.138.100 attack
Jun  9 20:27:07 vps46666688 sshd[13368]: Failed password for root from 61.155.138.100 port 48454 ssh2
...
2020-06-10 07:32:37
178.124.171.139 attackspam
Automatic report - Banned IP Access
2020-06-10 07:53:22
106.12.16.2 attackbotsspam
2020-06-09T21:47:16.399486shield sshd\[17666\]: Invalid user nagios from 106.12.16.2 port 42774
2020-06-09T21:47:16.403121shield sshd\[17666\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.16.2
2020-06-09T21:47:18.042080shield sshd\[17666\]: Failed password for invalid user nagios from 106.12.16.2 port 42774 ssh2
2020-06-09T21:51:12.307515shield sshd\[19316\]: Invalid user gwd from 106.12.16.2 port 40168
2020-06-09T21:51:12.311078shield sshd\[19316\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.16.2
2020-06-10 08:03:50
45.201.153.176 attackbots
Port Scan detected!
...
2020-06-10 08:02:24
138.197.210.82 attackspam
 TCP (SYN) 138.197.210.82:48778 -> port 27357, len 44
2020-06-10 07:39:56
165.227.101.226 attackspam
Jun 10 01:25:15 server sshd[31717]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.101.226
Jun 10 01:25:17 server sshd[31717]: Failed password for invalid user manorel from 165.227.101.226 port 41968 ssh2
Jun 10 01:28:10 server sshd[31886]: Failed password for root from 165.227.101.226 port 43334 ssh2
...
2020-06-10 07:28:53
39.98.245.32 attackbotsspam
Invalid user ftpuser from 39.98.245.32 port 58740
2020-06-10 07:45:50
183.17.230.250 attackbots
20/6/9@16:17:02: FAIL: Alarm-Network address from=183.17.230.250
20/6/9@16:17:02: FAIL: Alarm-Network address from=183.17.230.250
...
2020-06-10 07:42:28
45.55.72.69 attack
Jun 10 01:34:56 server sshd[32402]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.72.69
Jun 10 01:34:58 server sshd[32402]: Failed password for invalid user od123 from 45.55.72.69 port 52652 ssh2
Jun 10 01:38:21 server sshd[32693]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.72.69
...
2020-06-10 07:39:17
193.228.108.122 attackbotsspam
Jun  9 23:09:42 vps sshd[7181]: Failed password for root from 193.228.108.122 port 41908 ssh2
Jun  9 23:11:42 vps sshd[7276]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.228.108.122 
Jun  9 23:11:43 vps sshd[7276]: Failed password for invalid user men from 193.228.108.122 port 60270 ssh2
...
2020-06-10 07:43:36
165.22.51.37 attackspambots
2020-06-10T00:07:40+0200 Failed SSH Authentication/Brute Force Attack. (Server 4)
2020-06-10 07:47:23
193.56.28.176 attack
(smtpauth) Failed SMTP AUTH login from 193.56.28.176 (GB/United Kingdom/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SMTPAUTH; Logs: 2020-06-10 01:25:46 login authenticator failed for (User) [193.56.28.176]: 535 Incorrect authentication data (set_id=webmaster2@amsweb01.forhosting.nl)
2020-06-10 01:25:49 login authenticator failed for (User) [193.56.28.176]: 535 Incorrect authentication data (set_id=webmaster2@amsweb01.forhosting.nl)
2020-06-10 01:25:53 login authenticator failed for (User) [193.56.28.176]: 535 Incorrect authentication data (set_id=webmaster2@amsweb01.forhosting.nl)
2020-06-10 01:26:00 login authenticator failed for (User) [193.56.28.176]: 535 Incorrect authentication data (set_id=webmaster2@amsweb01.forhosting.nl)
2020-06-10 01:26:03 login authenticator failed for (User) [193.56.28.176]: 535 Incorrect authentication data (set_id=webmaster2@amsweb01.forhosting.nl)
2020-06-10 07:33:26
125.134.68.229 attack
Telnet Honeypot -> Telnet Bruteforce / Login
2020-06-10 07:48:57
192.241.151.77 attack
C1,WP GET /lappan/wp-login.php
2020-06-10 07:31:34

Recently Reported IPs

139.5.202.18 139.5.159.13 139.5.222.233 139.5.222.225
139.5.222.235 139.5.222.48 139.5.223.54 139.5.223.86
139.5.254.120 139.5.226.205 139.5.36.143 139.5.254.220
139.5.36.153 139.5.36.217 139.5.255.76 139.5.36.38
139.5.37.28 139.5.38.25 139.5.38.85 139.5.39.138