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

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
103.139.102.110 attackspam
3x Failed Password
2020-10-07 06:37:52
103.139.102.110 attackspambots
(sshd) Failed SSH login from 103.139.102.110 (VN/Vietnam/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct  6 05:44:17 optimus sshd[30470]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.139.102.110  user=root
Oct  6 05:44:19 optimus sshd[30470]: Failed password for root from 103.139.102.110 port 49499 ssh2
Oct  6 05:52:36 optimus sshd[1018]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.139.102.110  user=root
Oct  6 05:52:37 optimus sshd[1018]: Failed password for root from 103.139.102.110 port 60602 ssh2
Oct  6 05:56:33 optimus sshd[2259]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.139.102.110  user=root
2020-10-06 22:56:00
103.139.102.110 attackbotsspam
Sep 15 15:37:59 ip106 sshd[14014]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.139.102.110 
Sep 15 15:38:01 ip106 sshd[14014]: Failed password for invalid user abcd.1234 from 103.139.102.110 port 36060 ssh2
...
2020-09-15 23:42:04
103.139.102.110 attackbotsspam
$f2bV_matches
2020-09-15 15:34:08
103.139.190.15 attackspam
(smtpauth) Failed SMTP AUTH login from 103.139.190.15 (IN/India/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-08-27 08:25:12 plain authenticator failed for ([103.139.190.15]) [103.139.190.15]: 535 Incorrect authentication data (set_id=info)
2020-08-27 12:59:05
103.139.190.18 attackbotsspam
$f2bV_matches
2020-08-21 04:46:44
103.139.102.110 attackbotsspam
Aug 20 16:04:36 firewall sshd[28620]: Failed password for invalid user gas from 103.139.102.110 port 50922 ssh2
Aug 20 16:08:42 firewall sshd[28761]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.139.102.110  user=root
Aug 20 16:08:44 firewall sshd[28761]: Failed password for root from 103.139.102.110 port 50922 ssh2
...
2020-08-21 03:29:40
103.139.120.233 attackbots
Automatic report - Port Scan Attack
2020-08-20 14:22:45
103.139.113.34 attackspambots
MYH,DEF GET /errors/adminer-4.6.5.php
GET /errors/adminer-4.6.5.php
GET /errors/adminer-4.6.5.php
GET /errors/adminer-4.6.5.php
GET /errors/adminer-4.6.5.php
GET /errors/adminer-4.6.5.php
2020-08-20 03:04:50
103.139.102.110 attackspam
Aug  4 19:00:23 gospond sshd[10488]: Failed password for root from 103.139.102.110 port 39419 ssh2
Aug  4 19:00:21 gospond sshd[10488]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.139.102.110  user=root
Aug  4 19:00:23 gospond sshd[10488]: Failed password for root from 103.139.102.110 port 39419 ssh2
...
2020-08-05 03:04:25
103.139.102.110 attack
Aug  2 07:31:37 webhost01 sshd[23659]: Failed password for root from 103.139.102.110 port 51934 ssh2
...
2020-08-02 09:07:35
103.139.102.110 attack
Aug  1 14:34:32 ajax sshd[26032]: Failed password for root from 103.139.102.110 port 58154 ssh2
2020-08-01 21:42:14
103.139.171.220 attackspambots
port scan and connect, tcp 80 (http)
2020-07-26 06:20:27
103.139.113.34 attackbotsspam
MYH,DEF GET /js/adminer-3.7.1.php
GET /js/adminer-3.7.1.php
GET /js/adminer-3.7.1.php
GET /js/adminer-3.7.1.php
GET /js/adminer-3.7.1.php
2020-07-10 00:50:36
103.139.19.90 attackbotsspam
DATE:2020-06-20 05:54:27, IP:103.139.19.90, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc)
2020-06-20 13:39:42
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 103.139.1.194
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 29835
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;103.139.1.194.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu May 19 02:47:36 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 194.1.139.103.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 194.1.139.103.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
45.249.111.40 attackbots
Nov 12 05:16:11 localhost sshd\[22240\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.249.111.40  user=root
Nov 12 05:16:13 localhost sshd\[22240\]: Failed password for root from 45.249.111.40 port 60426 ssh2
Nov 12 05:20:38 localhost sshd\[22419\]: Invalid user askey from 45.249.111.40 port 40990
Nov 12 05:20:38 localhost sshd\[22419\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.249.111.40
Nov 12 05:20:40 localhost sshd\[22419\]: Failed password for invalid user askey from 45.249.111.40 port 40990 ssh2
...
2019-11-12 13:28:37
120.224.187.89 attackspam
Date:	11/11 19:00:01 	Name:	PROTOCOL-SCADA Moxa discovery packet information disclosure attempt
Priority:	2 	Type:	Attempted Information Leak
IP info: 	120.224.187.89:46993 -> 10.0.0.1:4800
References:	none found	SID: 	42016
2019-11-12 13:31:44
106.75.176.111 attackspam
Nov 12 05:18:43 localhost sshd\[22344\]: Invalid user 12233E+11 from 106.75.176.111 port 43668
Nov 12 05:18:43 localhost sshd\[22344\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.176.111
Nov 12 05:18:45 localhost sshd\[22344\]: Failed password for invalid user 12233E+11 from 106.75.176.111 port 43668 ssh2
Nov 12 05:30:47 localhost sshd\[22695\]: Invalid user ffffffff from 106.75.176.111 port 57596
Nov 12 05:30:47 localhost sshd\[22695\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.176.111
...
2019-11-12 13:32:47
94.23.204.136 attack
Nov 11 19:23:22 hanapaa sshd\[24576\]: Invalid user winz from 94.23.204.136
Nov 11 19:23:22 hanapaa sshd\[24576\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns364702.ip-94-23-204.eu
Nov 11 19:23:24 hanapaa sshd\[24576\]: Failed password for invalid user winz from 94.23.204.136 port 36928 ssh2
Nov 11 19:26:59 hanapaa sshd\[24891\]: Invalid user welham from 94.23.204.136
Nov 11 19:26:59 hanapaa sshd\[24891\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns364702.ip-94-23-204.eu
2019-11-12 13:38:50
104.248.151.112 attackbotsspam
WordPress login Brute force / Web App Attack on client site.
2019-11-12 13:10:34
186.236.120.42 attack
port scan and connect, tcp 23 (telnet)
2019-11-12 13:13:32
91.213.119.246 attack
postfix
2019-11-12 13:28:13
182.122.184.209 attackbotsspam
Fail2Ban Ban Triggered
2019-11-12 13:41:44
77.42.79.69 attackbots
Automatic report - Port Scan Attack
2019-11-12 13:26:28
115.61.114.86 attackspambots
Fail2Ban Ban Triggered
2019-11-12 13:32:16
118.173.28.129 attackbots
Telnetd brute force attack detected by fail2ban
2019-11-12 13:03:21
81.23.109.186 attackbots
Autoban   81.23.109.186 AUTH/CONNECT
2019-11-12 13:41:18
218.29.83.34 attackspam
Nov 12 05:58:29 pornomens sshd\[10762\]: Invalid user support from 218.29.83.34 port 46838
Nov 12 05:58:29 pornomens sshd\[10762\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.29.83.34
Nov 12 05:58:31 pornomens sshd\[10762\]: Failed password for invalid user support from 218.29.83.34 port 46838 ssh2
...
2019-11-12 13:21:18
125.167.178.202 attackspam
Unauthorised access (Nov 12) SRC=125.167.178.202 LEN=52 TTL=116 ID=21124 DF TCP DPT=445 WINDOW=8192 SYN
2019-11-12 13:25:45
218.75.207.11 attackbotsspam
Automatic report - Banned IP Access
2019-11-12 13:34:57

Recently Reported IPs

103.139.1.18 103.139.1.225 103.139.1.23 103.139.103.165
103.139.103.35 103.139.16.190 103.139.196.131 103.139.196.132
103.139.196.135 103.139.196.217 103.139.196.68 103.139.196.94
103.139.197.160 103.139.243.5 103.139.43.131 83.39.17.192
103.139.48.117 103.139.48.59 103.139.48.61 103.139.48.66