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: Netherlands (the)

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

;; QUESTION SECTION:
;81.85.206.34.			IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 21 05:34:21 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 34.206.85.81.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 34.206.85.81.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
157.245.58.40 attack
20 attempts against mh_ha-misbehave-ban on air
2020-01-24 04:44:35
165.22.123.148 attackspam
WordPress attack, URL redirect, SQL infect
2020-01-24 04:39:42
199.223.232.221 attack
SSH bruteforce (Triggered fail2ban)
2020-01-24 05:13:36
73.239.220.42 attackspambots
Unauthorized connection attempt detected from IP address 73.239.220.42 to port 22 [J]
2020-01-24 04:49:29
112.103.198.2 attackspambots
unauthorized connection attempt
2020-01-24 05:07:09
188.217.244.81 attackspam
Unauthorized connection attempt detected from IP address 188.217.244.81 to port 80 [J]
2020-01-24 05:09:19
92.63.196.10 attackbots
34282/tcp 34254/tcp 34230/tcp...
[2019-11-29/2020-01-23]4057pkt,1437pt.(tcp)
2020-01-24 04:34:46
52.201.233.18 attackbotsspam
Jan 23 17:50:12 localhost sshd\[24928\]: Invalid user john from 52.201.233.18 port 56030
Jan 23 17:50:12 localhost sshd\[24928\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.201.233.18
Jan 23 17:50:14 localhost sshd\[24928\]: Failed password for invalid user john from 52.201.233.18 port 56030 ssh2
2020-01-24 04:32:05
101.88.36.27 attackspam
Lines containing failures of 101.88.36.27


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=101.88.36.27
2020-01-24 04:58:44
106.54.142.84 attack
$f2bV_matches
2020-01-24 04:52:32
89.151.170.242 attack
Unauthorized connection attempt detected from IP address 89.151.170.242 to port 23 [J]
2020-01-24 04:59:11
106.13.97.37 attack
$f2bV_matches
2020-01-24 04:40:09
106.13.22.60 attack
$f2bV_matches
2020-01-24 04:47:06
222.186.42.4 attackbotsspam
Jan 23 21:37:17 mail sshd[21367]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.4  user=root
Jan 23 21:37:20 mail sshd[21367]: Failed password for root from 222.186.42.4 port 32994 ssh2
...
2020-01-24 04:39:22
138.197.129.38 attackspam
Jan 23 20:11:31 hcbbdb sshd\[900\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.129.38  user=root
Jan 23 20:11:33 hcbbdb sshd\[900\]: Failed password for root from 138.197.129.38 port 45974 ssh2
Jan 23 20:14:26 hcbbdb sshd\[1334\]: Invalid user test from 138.197.129.38
Jan 23 20:14:26 hcbbdb sshd\[1334\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.129.38
Jan 23 20:14:28 hcbbdb sshd\[1334\]: Failed password for invalid user test from 138.197.129.38 port 44692 ssh2
2020-01-24 04:42:56

Recently Reported IPs

255.164.188.234 115.185.126.194 206.34.0.23 161.94.52.173
151.188.52.250 64.27.100.105 174.15.115.12 224.60.87.33
156.223.25.11 8.244.63.197 42.226.189.118 137.14.105.26
153.77.28.16 33.235.28.137 156.81.49.222 145.205.127.79
37.68.175.167 155.139.62.94 94.102.55.1 116.20.107.19