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

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

;; QUESTION SECTION:
;85.182.12.142.			IN	A

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

;; Query time: 33 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 02:37:13 CST 2025
;; MSG SIZE  rcvd: 106
Host info
142.12.182.85.in-addr.arpa domain name pointer dynamic-085-182-012-142.85.182.12.pool.telefonica.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
142.12.182.85.in-addr.arpa	name = dynamic-085-182-012-142.85.182.12.pool.telefonica.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
113.125.25.73 attackspambots
Dec 13 11:29:30 localhost sshd\[10839\]: Invalid user sdu from 113.125.25.73 port 46848
Dec 13 11:29:30 localhost sshd\[10839\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.125.25.73
Dec 13 11:29:32 localhost sshd\[10839\]: Failed password for invalid user sdu from 113.125.25.73 port 46848 ssh2
2019-12-13 22:15:46
105.255.166.218 attackbotsspam
1576222985 - 12/13/2019 08:43:05 Host: 105.255.166.218/105.255.166.218 Port: 445 TCP Blocked
2019-12-13 22:00:13
52.53.162.57 attack
Port scan on 1 port(s): 53
2019-12-13 22:36:43
175.126.37.156 attackbots
Dec 13 11:59:55 serwer sshd\[20449\]: Invalid user yauch from 175.126.37.156 port 47057
Dec 13 11:59:55 serwer sshd\[20449\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.126.37.156
Dec 13 11:59:57 serwer sshd\[20449\]: Failed password for invalid user yauch from 175.126.37.156 port 47057 ssh2
...
2019-12-13 22:34:15
45.143.220.76 attack
Dec 13 16:59:14 debian-2gb-vpn-nbg1-1 kernel: [623931.533455] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=45.143.220.76 DST=78.46.192.101 LEN=443 TOS=0x00 PREC=0x00 TTL=54 ID=25782 DF PROTO=UDP SPT=5062 DPT=5060 LEN=423
2019-12-13 22:18:33
68.183.134.134 attack
xmlrpc attack
2019-12-13 22:38:21
1.171.15.110 attack
Scanning
2019-12-13 22:21:39
122.51.59.149 attack
sshd jail - ssh hack attempt
2019-12-13 22:43:36
185.63.218.225 attackbotsspam
[portscan] Port scan
2019-12-13 22:28:40
171.244.51.114 attackspam
$f2bV_matches
2019-12-13 22:23:03
88.230.168.131 attackspambots
SSH bruteforce
2019-12-13 22:08:50
183.107.76.55 attack
Brute force attack originating in KR.  Using IMAP against O365 account
2019-12-13 22:32:49
200.149.231.50 attackbots
$f2bV_matches
2019-12-13 22:20:06
51.254.204.190 attackspambots
$f2bV_matches
2019-12-13 22:06:16
106.13.4.172 attackbots
2019-12-08 07:10:57,282 fail2ban.actions        \[3073\]: NOTICE  \[ssh\] Ban 106.13.4.172
2019-12-08 07:34:11,885 fail2ban.actions        \[3073\]: NOTICE  \[ssh\] Ban 106.13.4.172
2019-12-08 07:55:24,975 fail2ban.actions        \[3073\]: NOTICE  \[ssh\] Ban 106.13.4.172
2019-12-08 08:17:04,968 fail2ban.actions        \[3073\]: NOTICE  \[ssh\] Ban 106.13.4.172
2019-12-08 08:38:47,867 fail2ban.actions        \[3073\]: NOTICE  \[ssh\] Ban 106.13.4.172
...
2019-12-13 22:07:24

Recently Reported IPs

186.221.57.12 103.228.33.13 209.40.230.12 42.158.52.100
103.98.75.74 135.45.178.137 175.126.252.231 27.209.145.26
177.237.102.26 212.164.174.186 210.49.8.246 72.146.193.239
235.161.75.114 104.123.171.97 142.230.58.165 57.43.27.207
54.50.11.201 215.186.219.23 96.120.23.251 57.30.217.82