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

;; QUESTION SECTION:
;139.11.169.112.			IN	A

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

;; Query time: 40 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 04:29:54 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 112.169.11.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 112.169.11.139.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
109.132.116.56 attackbots
Sep  3 08:09:04 server dovecot: imap-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=109.132.116.56, lip=172.104.140.148, session=
Sep  3 08:09:10 server dovecot: imap-login: Aborted login (auth failed, 1 attempts in 6 secs): user=, method=PLAIN, rip=109.132.116.56, lip=172.104.140.148, session=
Sep  3 08:09:10 server dovecot: imap-login: Aborted login (auth failed, 1 attempts in 6 secs): user=, method=PLAIN, rip=109.132.116.56, lip=172.104.140.148, session=
Sep  3 08:09:21 server dovecot: imap-login: Aborted login (auth failed, 1 attempts in 6 secs): user=, method=PLAIN, rip=109.132.116.56, lip=172.104.140.148, session=
Sep  3 08:09:23 server dovecot: imap-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=109.132.116.56, lip=172.104.140.14
...
2020-09-03 17:47:59
180.76.158.36 attackspambots
Sep  3 09:37:14 web-main sshd[379486]: Invalid user master from 180.76.158.36 port 46586
Sep  3 09:37:17 web-main sshd[379486]: Failed password for invalid user master from 180.76.158.36 port 46586 ssh2
Sep  3 09:52:42 web-main sshd[381424]: Invalid user rqh from 180.76.158.36 port 52678
2020-09-03 17:53:38
185.220.102.244 attack
2020-09-03 04:41:23.997642-0500  localhost sshd[82953]: Failed password for root from 185.220.102.244 port 20096 ssh2
2020-09-03 17:57:44
122.137.199.9 attackspam
[portscan] Port scan
2020-09-03 17:55:10
69.172.94.25 attackbotsspam
Port probing on unauthorized port 445
2020-09-03 17:48:21
185.220.101.207 attackspam
2020-09-03 04:32:16.849049-0500  localhost sshd[81859]: Failed password for root from 185.220.101.207 port 10322 ssh2
2020-09-03 18:01:30
212.115.235.71 attack
" "
2020-09-03 17:30:53
189.213.101.238 attackbotsspam
20/9/2@12:42:17: FAIL: Alarm-Telnet address from=189.213.101.238
...
2020-09-03 18:03:20
46.59.37.195 attackspam
2020-09-03T03:22:30.177047abusebot-4.cloudsearch.cf sshd[20527]: Invalid user admin from 46.59.37.195 port 33494
2020-09-03T03:22:30.215518abusebot-4.cloudsearch.cf sshd[20527]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=h-37-195.a328.priv.bahnhof.se
2020-09-03T03:22:30.177047abusebot-4.cloudsearch.cf sshd[20527]: Invalid user admin from 46.59.37.195 port 33494
2020-09-03T03:22:32.522703abusebot-4.cloudsearch.cf sshd[20527]: Failed password for invalid user admin from 46.59.37.195 port 33494 ssh2
2020-09-03T03:22:33.211253abusebot-4.cloudsearch.cf sshd[20531]: Invalid user support from 46.59.37.195 port 33527
2020-09-03T03:22:33.249901abusebot-4.cloudsearch.cf sshd[20531]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=h-37-195.a328.priv.bahnhof.se
2020-09-03T03:22:33.211253abusebot-4.cloudsearch.cf sshd[20531]: Invalid user support from 46.59.37.195 port 33527
2020-09-03T03:22:35.228858abusebot-4.clo
...
2020-09-03 17:34:50
2a01:4f8:192:3e4::2 attackbotsspam
20 attempts against mh-misbehave-ban on cedar
2020-09-03 17:59:47
51.83.98.104 attackspambots
Sep  3 11:21:20 minden010 sshd[5172]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.83.98.104
Sep  3 11:21:22 minden010 sshd[5172]: Failed password for invalid user wanglj from 51.83.98.104 port 48286 ssh2
Sep  3 11:25:14 minden010 sshd[6582]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.83.98.104
...
2020-09-03 17:49:41
185.239.242.195 attackbots
SSH-BruteForce
2020-09-03 17:37:29
87.246.7.25 attackspam
(smtpauth) Failed SMTP AUTH login from 87.246.7.25 (BG/Bulgaria/25.0-255.7.246.87.in-addr.arpa): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-09-03 01:27:03 login authenticator failed for (2DwMSGgRT) [87.246.7.25]: 535 Incorrect authentication data (set_id=info@safanicu.com)
2020-09-03 17:23:55
128.199.146.93 attack
2020-09-03T05:54:00.803413abusebot-4.cloudsearch.cf sshd[22273]: Invalid user guest from 128.199.146.93 port 51384
2020-09-03T05:54:00.809121abusebot-4.cloudsearch.cf sshd[22273]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.146.93
2020-09-03T05:54:00.803413abusebot-4.cloudsearch.cf sshd[22273]: Invalid user guest from 128.199.146.93 port 51384
2020-09-03T05:54:02.937725abusebot-4.cloudsearch.cf sshd[22273]: Failed password for invalid user guest from 128.199.146.93 port 51384 ssh2
2020-09-03T06:03:52.147173abusebot-4.cloudsearch.cf sshd[22537]: Invalid user hadoop from 128.199.146.93 port 58616
2020-09-03T06:03:52.154205abusebot-4.cloudsearch.cf sshd[22537]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.146.93
2020-09-03T06:03:52.147173abusebot-4.cloudsearch.cf sshd[22537]: Invalid user hadoop from 128.199.146.93 port 58616
2020-09-03T06:03:54.224230abusebot-4.cloudsearch.cf sshd[22537
...
2020-09-03 17:22:56
174.217.29.244 attackbots
Brute forcing email accounts
2020-09-03 17:40:29

Recently Reported IPs

94.210.240.160 162.34.85.109 222.216.247.63 164.108.184.68
235.220.124.171 165.82.131.132 113.90.89.4 174.200.93.147
14.219.138.87 128.162.133.207 159.56.187.144 27.180.122.38
27.124.27.104 19.91.44.25 3.237.254.200 124.229.65.197
7.255.197.111 249.84.47.137 42.141.203.36 81.179.180.164