85.245.131.41 - IPInfo

Basic Info

City: unknown

Region: unknown

Country: Portugal

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

;; QUESTION SECTION:
;85.245.131.41.			IN	A

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

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jan 25 21:12:24 CST 2025
;; MSG SIZE  rcvd: 106

Host info

41.131.245.85.in-addr.arpa domain name pointer bl12-131-41.dsl.telepac.pt.

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
41.131.245.85.in-addr.arpa	name = bl12-131-41.dsl.telepac.pt.

Authoritative answers can be found from:

Related IP info:

Related comments:

IP	Type	Details	Datetime
82.188.133.50	attack	Oct 14 21:51:16 imap-login: Info: Disconnected $no auth attempts in 0 secs$: user=\<\>, rip=82.188.133.50, lip=192.168.100.101, session=\\ Oct 14 21:52:12 imap-login: Info: Disconnected $no auth attempts in 0 secs$: user=\<\>, rip=82.188.133.50, lip=192.168.100.101, session=\\ Oct 14 21:52:19 imap-login: Info: Disconnected $auth failed, 1 attempts in 6 secs$: user=\, method=PLAIN, rip=82.188.133.50, lip=192.168.100.101, session=\\ Oct 14 21:52:28 imap-login: Info: Disconnected $no auth attempts in 0 secs$: user=\<\>, rip=82.188.133.50, lip=192.168.100.101, session=\\ Oct 14 21:52:29 imap-login: Info: Disconnected $no auth attempts in 0 secs$: user=\<\>, rip=82.188.133.50, lip=192.168.100.101, session=\\ Oct 14 21:52:32 imap-login: Info: Disconnected $no auth attempts in 0 secs$: user=\<\>, rip=82.188.133.50, lip=192.168.100.101, session=\\ Oct 14 21:52:32 imap-log	2019-10-15 06:35:34
101.226.168.96	attack	Port Scan detected from 101.226.168.96 (CN/China/-). 4 hits in the last 185 seconds	2019-10-15 06:55:30
83.171.99.217	attackspam	Oct 15 00:05:11 vmanager6029 sshd\[23301\]: Invalid user starcraft2 from 83.171.99.217 port 15191 Oct 15 00:05:11 vmanager6029 sshd\[23301\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.171.99.217 Oct 15 00:05:14 vmanager6029 sshd\[23301\]: Failed password for invalid user starcraft2 from 83.171.99.217 port 15191 ssh2	2019-10-15 06:52:53
176.31.253.55	attackbots	$f2bV_matches	2019-10-15 06:36:45
219.153.106.35	attackspam	Oct 14 17:19:59 mail sshd\[16037\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.153.106.35 user=root ...	2019-10-15 06:58:48
138.197.140.184	attackspambots	Oct 14 23:37:13 * sshd[23583]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.140.184 Oct 14 23:37:15 * sshd[23583]: Failed password for invalid user 12345 from 138.197.140.184 port 48164 ssh2	2019-10-15 06:56:37
51.38.37.128	attackbotsspam	Automatic report - Banned IP Access	2019-10-15 06:47:32
210.17.195.138	attackbotsspam	Oct 14 10:40:30 php1 sshd\[14163\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.17.195.138 user=root Oct 14 10:40:32 php1 sshd\[14163\]: Failed password for root from 210.17.195.138 port 44404 ssh2 Oct 14 10:44:26 php1 sshd\[14482\]: Invalid user mmk from 210.17.195.138 Oct 14 10:44:26 php1 sshd\[14482\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.17.195.138 Oct 14 10:44:28 php1 sshd\[14482\]: Failed password for invalid user mmk from 210.17.195.138 port 54958 ssh2	2019-10-15 07:01:33
158.69.192.214	attackspam	Invalid user jgdl from 158.69.192.214 port 34932	2019-10-15 06:27:09
178.46.164.91	attack	IMAP brute force ...	2019-10-15 06:45:12
124.41.211.27	attackbotsspam	Invalid user ppp from 124.41.211.27 port 48364	2019-10-15 07:03:30
49.235.107.14	attackspambots	2019-10-14T22:17:58.108495shield sshd\[17395\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.107.14 user=root 2019-10-14T22:18:00.521881shield sshd\[17395\]: Failed password for root from 49.235.107.14 port 33887 ssh2 2019-10-14T22:22:56.770456shield sshd\[17945\]: Invalid user prueba from 49.235.107.14 port 51632 2019-10-14T22:22:56.775315shield sshd\[17945\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.107.14 2019-10-14T22:22:58.431061shield sshd\[17945\]: Failed password for invalid user prueba from 49.235.107.14 port 51632 ssh2	2019-10-15 06:32:41
14.136.118.138	attack	2019-10-14T22:28:46.904675abusebot-5.cloudsearch.cf sshd\[28275\]: Invalid user kernel from 14.136.118.138 port 39018	2019-10-15 06:31:11
45.114.143.201	attackbotsspam	Oct 14 21:36:06 apollo sshd\[14297\]: Failed password for root from 45.114.143.201 port 46114 ssh2Oct 14 21:51:24 apollo sshd\[14370\]: Failed password for root from 45.114.143.201 port 37366 ssh2Oct 14 21:55:21 apollo sshd\[14385\]: Failed password for root from 45.114.143.201 port 48360 ssh2 ...	2019-10-15 06:41:15
185.90.118.103	attack	10/14/2019-18:25:16.817347 185.90.118.103 Protocol: 6 ET SCAN Potential SSH Scan	2019-10-15 06:28:32

Recently Reported IPs

215.171.248.231	69.32.76.73	146.81.176.24	201.148.177.38
236.30.101.107	247.0.206.3	215.23.148.109	167.177.79.16
15.105.201.194	106.203.202.16	223.39.168.205	56.111.200.109
206.174.107.2	78.89.16.97	175.66.70.33	245.178.170.31
211.27.179.125	24.155.183.5	91.21.9.6	164.3.116.195