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

;; QUESTION SECTION:
;31.18.80.166.			IN	A

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

;; Query time: 153 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 22 09:21:53 CST 2025
;; MSG SIZE  rcvd: 105
Host info
166.80.18.31.in-addr.arpa domain name pointer ip1f1250a6.dynamic.kabel-deutschland.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
166.80.18.31.in-addr.arpa	name = ip1f1250a6.dynamic.kabel-deutschland.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
89.248.162.136 attackbotsspam
Feb 13 06:37:19 debian-2gb-nbg1-2 kernel: \[3831468.231299\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=89.248.162.136 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=60082 PROTO=TCP SPT=46193 DPT=2626 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-13 14:10:58
121.46.250.178 attackbots
Feb 13 06:48:56 markkoudstaal sshd[15560]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.46.250.178
Feb 13 06:48:58 markkoudstaal sshd[15560]: Failed password for invalid user beagle from 121.46.250.178 port 47906 ssh2
Feb 13 06:51:19 markkoudstaal sshd[15981]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.46.250.178
2020-02-13 14:20:46
106.12.192.204 attack
Invalid user nagios from 106.12.192.204 port 47192
2020-02-13 14:53:13
103.206.137.90 attack
20/2/12@23:54:18: FAIL: Alarm-Network address from=103.206.137.90
20/2/12@23:54:19: FAIL: Alarm-Network address from=103.206.137.90
...
2020-02-13 14:09:05
70.45.133.188 attackbots
Feb 13 05:59:20 game-panel sshd[10044]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=70.45.133.188
Feb 13 05:59:23 game-panel sshd[10044]: Failed password for invalid user wisdom_curric from 70.45.133.188 port 40506 ssh2
Feb 13 06:03:45 game-panel sshd[10239]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=70.45.133.188
2020-02-13 14:16:00
222.186.175.163 attackspambots
2020-02-13T06:27:58.718492abusebot-3.cloudsearch.cf sshd[2662]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.163  user=root
2020-02-13T06:28:00.610066abusebot-3.cloudsearch.cf sshd[2662]: Failed password for root from 222.186.175.163 port 63236 ssh2
2020-02-13T06:28:04.741326abusebot-3.cloudsearch.cf sshd[2662]: Failed password for root from 222.186.175.163 port 63236 ssh2
2020-02-13T06:27:58.718492abusebot-3.cloudsearch.cf sshd[2662]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.163  user=root
2020-02-13T06:28:00.610066abusebot-3.cloudsearch.cf sshd[2662]: Failed password for root from 222.186.175.163 port 63236 ssh2
2020-02-13T06:28:04.741326abusebot-3.cloudsearch.cf sshd[2662]: Failed password for root from 222.186.175.163 port 63236 ssh2
2020-02-13T06:27:58.718492abusebot-3.cloudsearch.cf sshd[2662]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh
...
2020-02-13 14:38:16
116.206.40.44 attackbots
[Thu Feb 13 11:54:09.296635 2020] [:error] [pid 29333:tid 140024179844864] [client 116.206.40.44:58479] [client 116.206.40.44] ModSecurity: Access denied with code 403 (phase 4). Pattern match "^5\\\\d{2}$" at RESPONSE_STATUS. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/RESPONSE-950-DATA-LEAKAGES.conf"] [line "118"] [id "950100"] [msg "The Application Returned a 500-Level Status Code"] [data "Matched Data: 500 found within RESPONSE_STATUS: 500"] [severity "ERROR"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-disclosure"] [tag "WASCTC/WASC-13"] [tag "OWASP_TOP_10/A6"] [tag "PCI/6.5.6"] [tag "paranoia-level/2"] [hostname "karangploso.jatim.bmkg.go.id"] [uri "/images/1.svg"] [unique_id "XkTWZZOePmzR7ExralD6pQAAAU4"], referer: https://karangploso.jatim.bmkg.go.id/
...
2020-02-13 14:15:45
118.98.121.194 attackspam
(sshd) Failed SSH login from 118.98.121.194 (ID/Indonesia/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Feb 13 05:37:27 elude sshd[26613]: Invalid user brigit from 118.98.121.194 port 2661
Feb 13 05:37:30 elude sshd[26613]: Failed password for invalid user brigit from 118.98.121.194 port 2661 ssh2
Feb 13 05:50:33 elude sshd[27492]: Invalid user nagata from 118.98.121.194 port 36436
Feb 13 05:50:35 elude sshd[27492]: Failed password for invalid user nagata from 118.98.121.194 port 36436 ssh2
Feb 13 05:54:10 elude sshd[27803]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.98.121.194  user=root
2020-02-13 14:12:51
125.215.207.40 attackspam
Feb 12 20:16:13 hpm sshd\[6141\]: Invalid user topgun from 125.215.207.40
Feb 12 20:16:13 hpm sshd\[6141\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.215.207.40
Feb 12 20:16:14 hpm sshd\[6141\]: Failed password for invalid user topgun from 125.215.207.40 port 46740 ssh2
Feb 12 20:20:24 hpm sshd\[6568\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.215.207.40  user=root
Feb 12 20:20:27 hpm sshd\[6568\]: Failed password for root from 125.215.207.40 port 37596 ssh2
2020-02-13 14:40:12
125.160.112.154 attack
1581569635 - 02/13/2020 05:53:55 Host: 125.160.112.154/125.160.112.154 Port: 445 TCP Blocked
2020-02-13 14:26:08
91.98.126.102 attackbots
...
2020-02-13 14:31:06
103.243.81.252 attackbots
Absender hat Spam-Falle ausgel?st
2020-02-13 14:48:06
139.162.104.208 attack
Unauthorised access (Feb 13) SRC=139.162.104.208 LEN=40 TTL=246 ID=54321 TCP DPT=21 WINDOW=65535 SYN
2020-02-13 14:16:34
94.102.49.102 attackspambots
94.102.49.102 was recorded 11 times by 10 hosts attempting to connect to the following ports: 19,53,389,123. Incident counter (4h, 24h, all-time): 11, 19, 225
2020-02-13 14:27:28
149.5.209.159 attack
149.5.209.159 - - \[13/Feb/2020:05:53:48 +0100\] "POST /wp-login.php HTTP/1.0" 200 3080 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
149.5.209.159 - - \[13/Feb/2020:05:53:50 +0100\] "POST /wp-login.php HTTP/1.0" 200 3078 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
149.5.209.159 - - \[13/Feb/2020:05:53:51 +0100\] "POST /wp-login.php HTTP/1.0" 200 3050 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2020-02-13 14:28:43

Recently Reported IPs

162.98.228.223 27.112.193.51 174.140.210.5 96.215.116.225
235.95.15.187 222.17.215.67 157.161.162.119 92.219.186.9
51.145.178.205 169.17.190.168 163.35.74.62 144.219.155.112
96.88.79.203 166.209.187.40 71.206.246.217 123.231.83.214
187.203.219.113 33.137.185.98 202.14.65.255 92.238.240.19