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

;; QUESTION SECTION:
;116.203.85.214.			IN	A

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

;; Query time: 71 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 19 03:34:30 CST 2022
;; MSG SIZE  rcvd: 107
Host info
214.85.203.116.in-addr.arpa domain name pointer static.214.85.203.116.clients.your-server.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
214.85.203.116.in-addr.arpa	name = static.214.85.203.116.clients.your-server.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
218.61.47.132 attackspambots
Wordpress malicious attack:[sshd]
2020-05-06 12:52:21
170.254.195.104 attackbotsspam
May  6 05:56:38 haigwepa sshd[9895]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.254.195.104 
May  6 05:56:39 haigwepa sshd[9895]: Failed password for invalid user hldmserver from 170.254.195.104 port 51426 ssh2
...
2020-05-06 13:04:50
198.98.60.164 attackbotsspam
May  6 06:27:49 nginx sshd[4161]: Invalid user admin from 198.98.60.164
May  6 06:27:49 nginx sshd[4161]: Connection reset by 198.98.60.164 port 61991 [preauth]
2020-05-06 12:47:13
141.98.81.182 attack
[Tue May 05 22:24:24 2020] - Syn Flood From IP: 141.98.81.182 Port: 65534
2020-05-06 12:59:07
34.70.80.41 attackspambots
Unauthorized connection attempt detected from IP address 34.70.80.41 to port 23
2020-05-06 13:18:00
115.159.65.195 attack
leo_www
2020-05-06 13:12:44
222.186.190.14 attack
May  6 07:41:14 server2 sshd\[2791\]: User root from 222.186.190.14 not allowed because not listed in AllowUsers
May  6 07:41:15 server2 sshd\[2793\]: User root from 222.186.190.14 not allowed because not listed in AllowUsers
May  6 07:41:17 server2 sshd\[2795\]: User root from 222.186.190.14 not allowed because not listed in AllowUsers
May  6 07:41:53 server2 sshd\[2808\]: User root from 222.186.190.14 not allowed because not listed in AllowUsers
May  6 07:43:47 server2 sshd\[2865\]: User root from 222.186.190.14 not allowed because not listed in AllowUsers
May  6 07:49:03 server2 sshd\[3236\]: User root from 222.186.190.14 not allowed because not listed in AllowUsers
2020-05-06 12:55:22
139.59.169.103 attack
$f2bV_matches
2020-05-06 12:44:28
78.26.185.152 attackspambots
2020-05-05T23:34:37.7643561495-001 sshd[5341]: Invalid user ultra from 78.26.185.152 port 57592
2020-05-05T23:34:39.9783141495-001 sshd[5341]: Failed password for invalid user ultra from 78.26.185.152 port 57592 ssh2
2020-05-05T23:38:45.8475121495-001 sshd[5483]: Invalid user lk from 78.26.185.152 port 41182
2020-05-05T23:38:45.8511771495-001 sshd[5483]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=78.26.185.152
2020-05-05T23:38:45.8475121495-001 sshd[5483]: Invalid user lk from 78.26.185.152 port 41182
2020-05-05T23:38:48.1095711495-001 sshd[5483]: Failed password for invalid user lk from 78.26.185.152 port 41182 ssh2
...
2020-05-06 13:14:15
139.59.69.76 attackbotsspam
May  6 00:46:42 ny01 sshd[10019]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.69.76
May  6 00:46:45 ny01 sshd[10019]: Failed password for invalid user tracker from 139.59.69.76 port 37874 ssh2
May  6 00:51:44 ny01 sshd[10662]: Failed password for root from 139.59.69.76 port 47380 ssh2
2020-05-06 12:57:43
160.16.82.31 attackspam
May  6 06:42:47 debian-2gb-nbg1-2 kernel: \[10999059.354727\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=160.16.82.31 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=236 ID=19305 PROTO=TCP SPT=42501 DPT=44769 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-06 12:49:06
41.39.194.16 attackspambots
" "
2020-05-06 13:17:42
104.137.12.212 attackbots
Fail2Ban Ban Triggered
HTTP Bot Harvester Detected
2020-05-06 13:13:18
218.92.0.195 attack
05/06/2020-00:01:36.652253 218.92.0.195 Protocol: 6 ET SCAN Potential SSH Scan
2020-05-06 13:09:16
2002:b9ea:db69::b9ea:db69 attack
May  6 05:33:05 web01.agentur-b-2.de postfix/smtpd[84587]: warning: unknown[2002:b9ea:db69::b9ea:db69]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May  6 05:33:05 web01.agentur-b-2.de postfix/smtpd[84587]: lost connection after AUTH from unknown[2002:b9ea:db69::b9ea:db69]
May  6 05:34:23 web01.agentur-b-2.de postfix/smtpd[84587]: warning: unknown[2002:b9ea:db69::b9ea:db69]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May  6 05:34:23 web01.agentur-b-2.de postfix/smtpd[84587]: lost connection after AUTH from unknown[2002:b9ea:db69::b9ea:db69]
May  6 05:36:19 web01.agentur-b-2.de postfix/smtpd[83034]: warning: unknown[2002:b9ea:db69::b9ea:db69]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2020-05-06 12:34:26

Recently Reported IPs

116.203.95.229 116.254.101.100 116.66.197.23 116.71.128.142
116.90.50.34 116.90.165.5 117.102.75.171 117.103.66.53
117.197.126.98 117.196.68.215 116.3.202.22 117.195.82.17
117.176.150.231 117.198.218.190 117.204.253.237 117.204.254.31
117.20.63.58 117.251.195.85 117.30.39.128 117.4.179.121