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

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

;; QUESTION SECTION:
;93.164.148.21.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 15 11:00:45 CST 2025
;; MSG SIZE  rcvd: 106
Host info
21.148.164.93.in-addr.arpa domain name pointer 93-164-148-21-dynamic.dk.customer.tdc.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
21.148.164.93.in-addr.arpa	name = 93-164-148-21-dynamic.dk.customer.tdc.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
176.107.133.144 attackbots
Dec 13 18:50:47 debian-2gb-nbg1-2 kernel: \[24540978.927490\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=176.107.133.144 DST=195.201.40.59 LEN=437 TOS=0x00 PREC=0x00 TTL=55 ID=5200 DF PROTO=UDP SPT=5115 DPT=5060 LEN=417
2019-12-14 05:41:56
201.208.238.129 attack
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2019-12-14 05:23:55
201.155.194.196 attackspam
port scan and connect, tcp 23 (telnet)
2019-12-14 05:28:01
190.206.124.150 attackspambots
Attempt to attack host OS, exploiting network vulnerabilities, on 13-12-2019 15:55:10.
2019-12-14 05:11:18
14.63.174.149 attackspambots
(sshd) Failed SSH login from 14.63.174.149 (KR/South Korea/-): 3 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Dec 13 18:05:29 andromeda sshd[6669]: Invalid user FIELD from 14.63.174.149 port 33682
Dec 13 18:05:31 andromeda sshd[6669]: Failed password for invalid user FIELD from 14.63.174.149 port 33682 ssh2
Dec 13 18:13:24 andromeda sshd[7605]: Invalid user rodomantsev from 14.63.174.149 port 46441
2019-12-14 05:37:01
171.103.57.210 attackspam
failed_logins
2019-12-14 05:46:03
218.92.0.184 attack
2019-12-13T22:41:45.919975ns386461 sshd\[29354\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.184  user=root
2019-12-13T22:41:47.927819ns386461 sshd\[29354\]: Failed password for root from 218.92.0.184 port 34646 ssh2
2019-12-13T22:41:50.717612ns386461 sshd\[29354\]: Failed password for root from 218.92.0.184 port 34646 ssh2
2019-12-13T22:41:53.782469ns386461 sshd\[29354\]: Failed password for root from 218.92.0.184 port 34646 ssh2
2019-12-13T22:41:57.062647ns386461 sshd\[29354\]: Failed password for root from 218.92.0.184 port 34646 ssh2
...
2019-12-14 05:42:30
175.6.5.233 attackbotsspam
FTP Brute-Force reported by Fail2Ban
2019-12-14 05:45:34
45.143.221.23 attack
45.143.221.23 was recorded 13 times by 13 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 13, 39, 1051
2019-12-14 05:15:29
162.252.57.36 attack
SSH Brute-Forcing (server2)
2019-12-14 05:38:50
106.12.200.13 attack
Dec 14 04:31:01 webhost01 sshd[24978]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.200.13
Dec 14 04:31:03 webhost01 sshd[24978]: Failed password for invalid user nnnnn from 106.12.200.13 port 42344 ssh2
...
2019-12-14 05:37:15
159.203.201.190 attackbotsspam
*Port Scan* detected from 159.203.201.190 (US/United States/zg-0911a-225.stretchoid.com). 4 hits in the last 290 seconds
2019-12-14 05:21:33
46.38.251.50 attackbots
Dec 13 04:53:45 *** sshd[9244]: Failed password for invalid user naker from 46.38.251.50 port 51490 ssh2
Dec 13 04:58:42 *** sshd[9318]: Failed password for invalid user kunming from 46.38.251.50 port 60290 ssh2
Dec 13 05:08:32 *** sshd[9562]: Failed password for invalid user khorvash from 46.38.251.50 port 49654 ssh2
Dec 13 05:18:39 *** sshd[9801]: Failed password for invalid user schlenzig from 46.38.251.50 port 38968 ssh2
Dec 13 05:28:38 *** sshd[9993]: Failed password for invalid user boslar from 46.38.251.50 port 56530 ssh2
Dec 13 05:33:51 *** sshd[10081]: Failed password for invalid user couratin from 46.38.251.50 port 37098 ssh2
Dec 13 05:38:57 *** sshd[10163]: Failed password for invalid user zzz from 46.38.251.50 port 45900 ssh2
Dec 13 05:49:15 *** sshd[10471]: Failed password for invalid user test from 46.38.251.50 port 35216 ssh2
Dec 13 05:54:28 *** sshd[10555]: Failed password for invalid user test from 46.38.251.50 port 44016 ssh2
Dec 13 05:59:36 *** sshd[10623]: Failed password for invalid user
2019-12-14 05:30:34
200.188.129.178 attack
SSH bruteforce
2019-12-14 05:43:00
188.166.34.129 attack
Invalid user backup from 188.166.34.129 port 41326
2019-12-14 05:43:23

Recently Reported IPs

51.108.232.254 93.28.201.167 231.94.118.83 218.240.183.161
125.225.63.125 64.111.225.109 176.177.172.170 169.60.72.211
96.50.17.101 47.98.184.71 130.123.16.91 170.25.225.63
66.135.234.183 220.218.238.149 38.122.28.90 229.130.178.64
43.213.10.237 39.171.15.50 35.105.64.131 181.113.229.164