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

Internet Service Provider: Telenor Norge AS

Hostname: unknown

Organization: unknown

Usage Type: Mobile ISP

Comments:
Type Details Datetime
attackbotsspam
Lines containing failures of 85.164.29.199
/var/log/apache/pucorp.org.log.1:Feb  9 10:02:37 server01 postfix/smtpd[17253]: connect from ti0197a430-0707.bb.online.no[85.164.29.199]
/var/log/apache/pucorp.org.log.1:Feb x@x
/var/log/apache/pucorp.org.log.1:Feb x@x
/var/log/apache/pucorp.org.log.1:Feb  9 10:02:37 server01 postfix/policy-spf[17263]: : Policy action=PREPEND Received-SPF: none (att.net: No applicable sender policy available) receiver=x@x
/var/log/apache/pucorp.org.log.1:Feb x@x
/var/log/apache/pucorp.org.log.1:Feb  9 10:02:40 server01 postfix/smtpd[17253]: lost connection after DATA from ti0197a430-0707.bb.online.no[85.164.29.199]
/var/log/apache/pucorp.org.log.1:Feb  9 10:02:40 server01 postfix/smtpd[17253]: disconnect from ti0197a430-0707.bb.online.no[85.164.29.199]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=85.164.29.199
2020-02-17 02:09:24
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 85.164.29.199
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20532
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;85.164.29.199.			IN	A

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

;; Query time: 244 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 17 02:09:18 CST 2020
;; MSG SIZE  rcvd: 117
Host info
199.29.164.85.in-addr.arpa domain name pointer ti0197a430-0707.bb.online.no.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
199.29.164.85.in-addr.arpa	name = ti0197a430-0707.bb.online.no.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
172.104.242.173 attackbots
172.104.242.173 - - \[22/Nov/2019:19:28:57 +0100\] "9\xCD\xC3V\x8C\&\x12Dz/\xB7\xC0t\x96C\xE2" 400 166 "-" "-"
...
2019-11-25 19:57:12
183.100.204.194 attackbotsspam
Nov 25 06:54:03 l01 sshd[835011]: Did not receive identification string from 183.100.204.194
Nov 25 06:59:54 l01 sshd[835416]: Invalid user admin from 183.100.204.194
Nov 25 06:59:54 l01 sshd[835416]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.100.204.194 
Nov 25 06:59:56 l01 sshd[835416]: Failed password for invalid user admin from 183.100.204.194 port 35320 ssh2
Nov 25 07:00:55 l01 sshd[835473]: Invalid user ubuntu from 183.100.204.194
Nov 25 07:00:55 l01 sshd[835473]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.100.204.194 
Nov 25 07:00:56 l01 sshd[835473]: Failed password for invalid user ubuntu from 183.100.204.194 port 35572 ssh2
Nov 25 07:02:40 l01 sshd[835687]: Invalid user pi from 183.100.204.194
Nov 25 07:02:40 l01 sshd[835687]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.100.204.194 
Nov 25 07:02:42 l01 sshd[835687]:........
-------------------------------
2019-11-25 20:11:28
178.33.45.156 attackspam
SSH bruteforce
2019-11-25 19:59:20
201.91.231.154 attackspambots
Unauthorised access (Nov 25) SRC=201.91.231.154 LEN=52 TOS=0x10 PREC=0x40 TTL=115 ID=20486 DF TCP DPT=445 WINDOW=8192 SYN
2019-11-25 19:50:01
113.118.48.92 attack
SSH/22 MH Probe, BF, Hack -
2019-11-25 20:03:43
149.56.100.237 attackbotsspam
2019-11-25T10:31:09.756983abusebot.cloudsearch.cf sshd\[12651\]: Invalid user hanhb from 149.56.100.237 port 34976
2019-11-25 19:47:42
170.210.60.30 attack
Nov 25 01:02:48 kapalua sshd\[28409\]: Invalid user ap from 170.210.60.30
Nov 25 01:02:48 kapalua sshd\[28409\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.210.60.30
Nov 25 01:02:51 kapalua sshd\[28409\]: Failed password for invalid user ap from 170.210.60.30 port 54040 ssh2
Nov 25 01:10:53 kapalua sshd\[29560\]: Invalid user shimizukogyo from 170.210.60.30
Nov 25 01:10:53 kapalua sshd\[29560\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.210.60.30
2019-11-25 19:46:41
152.136.122.130 attackbots
Nov 25 07:38:41 vps691689 sshd[489]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.122.130
Nov 25 07:38:43 vps691689 sshd[489]: Failed password for invalid user smmsp from 152.136.122.130 port 33740 ssh2
Nov 25 07:46:50 vps691689 sshd[562]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.122.130
...
2019-11-25 20:26:51
58.47.79.182 attackspambots
[portscan] Port scan
2019-11-25 20:05:06
24.86.80.229 attackbotsspam
24.86.80.229 was recorded 5 times by 1 hosts attempting to connect to the following ports: 51413. Incident counter (4h, 24h, all-time): 5, 19, 19
2019-11-25 20:19:28
107.170.244.110 attackspam
SSH invalid-user multiple login attempts
2019-11-25 19:45:59
157.230.133.15 attackspambots
Nov 25 02:39:10 lvpxxxxxxx88-92-201-20 sshd[8991]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.133.15  user=games
Nov 25 02:39:12 lvpxxxxxxx88-92-201-20 sshd[8991]: Failed password for games from 157.230.133.15 port 47398 ssh2
Nov 25 02:39:12 lvpxxxxxxx88-92-201-20 sshd[8991]: Received disconnect from 157.230.133.15: 11: Bye Bye [preauth]
Nov 25 03:12:00 lvpxxxxxxx88-92-201-20 sshd[9557]: Failed password for invalid user info from 157.230.133.15 port 38878 ssh2
Nov 25 03:12:00 lvpxxxxxxx88-92-201-20 sshd[9557]: Received disconnect from 157.230.133.15: 11: Bye Bye [preauth]
Nov 25 03:17:56 lvpxxxxxxx88-92-201-20 sshd[9674]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.133.15  user=backup
Nov 25 03:17:57 lvpxxxxxxx88-92-201-20 sshd[9674]: Failed password for backup from 157.230.133.15 port 46154 ssh2
Nov 25 03:17:57 lvpxxxxxxx88-92-201-20 sshd[9674]: Received disconnect ........
-------------------------------
2019-11-25 19:48:58
195.181.38.107 attackspam
Caught in portsentry honeypot
2019-11-25 20:17:58
51.255.42.250 attackspam
Nov 25 11:28:14 localhost sshd\[76514\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.42.250  user=root
Nov 25 11:28:16 localhost sshd\[76514\]: Failed password for root from 51.255.42.250 port 55522 ssh2
Nov 25 11:36:13 localhost sshd\[76726\]: Invalid user admin from 51.255.42.250 port 45606
Nov 25 11:36:13 localhost sshd\[76726\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.42.250
Nov 25 11:36:15 localhost sshd\[76726\]: Failed password for invalid user admin from 51.255.42.250 port 45606 ssh2
...
2019-11-25 19:59:36
89.70.32.104 attackbotsspam
89.70.32.104 was recorded 5 times by 1 hosts attempting to connect to the following ports: 51413. Incident counter (4h, 24h, all-time): 5, 5, 5
2019-11-25 20:22:43

Recently Reported IPs

116.9.99.103 10.192.15.69 31.9.8.216 2.23.250.111
0.232.8.120 51.178.151.50 138.9.213.11 187.32.242.217
172.230.29.64 185.103.255.37 111.251.45.102 192.241.233.164
185.103.255.190 50.62.177.231 182.113.186.229 222.52.99.155
183.235.185.207 185.103.254.82 72.130.219.49 185.103.248.158