26.131.191.139

Basic Info

City: unknown

Region: unknown

Country: None

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:

Make a comment on this IP

No discussion about this IP yet. Click above link to make one.

Comments on same subnet:

No discussion about this subnet yet..

Whois info:

Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 26.131.191.139
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 45733
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;26.131.191.139.			IN	A

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

;; Query time: 90 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Mar 10 11:16:32 CST 2022
;; MSG SIZE  rcvd: 107

Host info

Host 139.191.131.26.in-addr.arpa. not found: 3(NXDOMAIN)

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 139.191.131.26.in-addr.arpa: NXDOMAIN

Related IP info:

Related comments:

IP	Type	Details	Datetime
207.180.232.135	attack	Fail2Ban Ban Triggered	2020-09-04 14:38:01
54.37.68.66	attackbotsspam	(sshd) Failed SSH login from 54.37.68.66 (FR/France/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 4 02:06:51 server4 sshd[12281]: Invalid user mysql2 from 54.37.68.66 Sep 4 02:06:52 server4 sshd[12281]: Failed password for invalid user mysql2 from 54.37.68.66 port 43892 ssh2 Sep 4 02:14:27 server4 sshd[19432]: Invalid user sa from 54.37.68.66 Sep 4 02:14:29 server4 sshd[19432]: Failed password for invalid user sa from 54.37.68.66 port 50900 ssh2 Sep 4 02:17:32 server4 sshd[21888]: Invalid user phil from 54.37.68.66	2020-09-04 14:26:54
95.213.243.71	attackspam	SSH Invalid Login	2020-09-04 14:41:03
105.235.135.204	attack	Sep 3 18:48:21 mellenthin postfix/smtpd[20928]: NOQUEUE: reject: RCPT from unknown[105.235.135.204]: 554 5.7.1 Service unavailable; Client host [105.235.135.204] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/105.235.135.204; from= to= proto=ESMTP helo=<[105.235.135.204]>	2020-09-04 14:36:07
37.47.176.148	attack	Lines containing failures of 37.47.176.148 Sep 2 10:23:11 omfg postfix/smtpd[30643]: connect from public-gprs395603.centertel.pl[37.47.176.148] Sep x@x Sep 2 10:23:11 omfg postfix/smtpd[30643]: lost connection after DATA from public-gprs395603.centertel.pl[37.47.176.148] Sep 2 10:23:11 omfg postfix/smtpd[30643]: disconnect from public-gprs395603.centertel.pl[37.47.176.148] ehlo=1 mail=1 rcpt=0/1 data=0/1 commands=2/4 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=37.47.176.148	2020-09-04 15:03:23
37.30.38.109	attackbots	Sep 3 18:48:34 mellenthin postfix/smtpd[20953]: NOQUEUE: reject: RCPT from 37.30.38.109.nat.umts.dynamic.t-mobile.pl[37.30.38.109]: 554 5.7.1 Service unavailable; Client host [37.30.38.109] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/37.30.38.109; from= to= proto=ESMTP helo=<37.30.38.109.nat.umts.dynamic.t-mobile.pl>	2020-09-04 14:25:53
51.89.14.136	attackbotsspam	2020-09-04 01:16:14.806350-0500 localhost smtpd[80512]: NOQUEUE: reject: RCPT from unknown[51.89.14.136]: 450 4.7.25 Client host rejected: cannot find your hostname, [51.89.14.136]; from= to= proto=ESMTP helo=	2020-09-04 14:51:33
41.144.80.18	attackbots	Sep 2 10:18:58 mxgate1 postfix/postscreen[17278]: CONNECT from [41.144.80.18]:29510 to [176.31.12.44]:25 Sep 2 10:18:58 mxgate1 postfix/dnsblog[17284]: addr 41.144.80.18 listed by domain zen.spamhaus.org as 127.0.0.4 Sep 2 10:18:58 mxgate1 postfix/dnsblog[17284]: addr 41.144.80.18 listed by domain zen.spamhaus.org as 127.0.0.10 Sep 2 10:18:58 mxgate1 postfix/dnsblog[17287]: addr 41.144.80.18 listed by domain cbl.abuseat.org as 127.0.0.2 Sep 2 10:18:58 mxgate1 postfix/dnsblog[17286]: addr 41.144.80.18 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2 Sep 2 10:18:58 mxgate1 postfix/dnsblog[17283]: addr 41.144.80.18 listed by domain b.barracudacentral.org as 127.0.0.2 Sep 2 10:19:04 mxgate1 postfix/postscreen[17278]: DNSBL rank 5 for [41.144.80.18]:29510 Sep x@x Sep 2 10:19:05 mxgate1 postfix/postscreen[17278]: HANGUP after 1.4 from [41.144.80.18]:29510 in tests after SMTP handshake Sep 2 10:19:05 mxgate1 postfix/postscreen[17278]: DISCONNECT [41.144.80.18]:29510 ........ -------------------------------	2020-09-04 14:42:48
146.0.41.70	attack	Sep 4 00:22:11 lanister sshd[25427]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=146.0.41.70 user=root Sep 4 00:22:13 lanister sshd[25427]: Failed password for root from 146.0.41.70 port 36316 ssh2 Sep 4 00:25:46 lanister sshd[25519]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=146.0.41.70 user=root Sep 4 00:25:48 lanister sshd[25519]: Failed password for root from 146.0.41.70 port 42092 ssh2	2020-09-04 14:40:45
177.200.68.157	attackbotsspam	Sep 3 18:47:55 mellenthin postfix/smtpd[20177]: NOQUEUE: reject: RCPT from 177-200-68-157.dynamic.skysever.com.br[177.200.68.157]: 554 5.7.1 Service unavailable; Client host [177.200.68.157] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/177.200.68.157; from= to= proto=ESMTP helo=<177-200-68-157.dynamic.skysever.com.br>	2020-09-04 14:59:54
112.85.42.200	attackspam	Sep 4 09:04:13 ncomp sshd[25578]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.200 user=root Sep 4 09:04:15 ncomp sshd[25578]: Failed password for root from 112.85.42.200 port 4096 ssh2 Sep 4 09:04:28 ncomp sshd[25578]: error: maximum authentication attempts exceeded for root from 112.85.42.200 port 4096 ssh2 [preauth] Sep 4 09:04:13 ncomp sshd[25578]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.200 user=root Sep 4 09:04:15 ncomp sshd[25578]: Failed password for root from 112.85.42.200 port 4096 ssh2 Sep 4 09:04:28 ncomp sshd[25578]: error: maximum authentication attempts exceeded for root from 112.85.42.200 port 4096 ssh2 [preauth]	2020-09-04 15:05:12
111.95.203.15	attack	Lines containing failures of 111.95.203.15 Sep 2 10:15:31 omfg postfix/smtpd[20612]: connect from unknown[111.95.203.15] Sep x@x ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=111.95.203.15	2020-09-04 14:27:24
218.104.128.54	attackspambots	Sep 4 00:47:33 ns382633 sshd\[16600\]: Invalid user digital from 218.104.128.54 port 60916 Sep 4 00:47:33 ns382633 sshd\[16600\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.104.128.54 Sep 4 00:47:35 ns382633 sshd\[16600\]: Failed password for invalid user digital from 218.104.128.54 port 60916 ssh2 Sep 4 01:03:53 ns382633 sshd\[19455\]: Invalid user postgres from 218.104.128.54 port 39639 Sep 4 01:03:53 ns382633 sshd\[19455\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.104.128.54	2020-09-04 14:24:07
65.50.209.87	attackbots	Sep 3 18:10:40 rush sshd[18829]: Failed password for root from 65.50.209.87 port 60326 ssh2 Sep 3 18:14:14 rush sshd[18943]: Failed password for root from 65.50.209.87 port 35028 ssh2 Sep 3 18:17:52 rush sshd[19052]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=65.50.209.87 ...	2020-09-04 14:57:47
189.234.178.212	attack	20/9/3@12:48:14: FAIL: Alarm-Network address from=189.234.178.212 20/9/3@12:48:14: FAIL: Alarm-Network address from=189.234.178.212 20/9/3@12:48:14: FAIL: Alarm-Network address from=189.234.178.212 ...	2020-09-04 14:40:30

Recently Reported IPs

124.122.70.248	124.122.70.32	124.122.70.52	124.122.70.58
124.122.70.86	124.122.71.116	124.122.71.119	124.122.71.149
124.122.71.150	124.122.71.17	124.122.71.172	124.122.71.219
124.122.71.238	178.95.244.38	124.122.99.64	124.122.99.66
124.122.99.68	216.131.218.202	124.122.99.70	124.122.99.72