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

;; QUESTION SECTION:
;93.242.212.72.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 22 23:54:41 CST 2025
;; MSG SIZE  rcvd: 106
Host info
72.212.242.93.in-addr.arpa domain name pointer p5df2d448.dip0.t-ipconnect.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
72.212.242.93.in-addr.arpa	name = p5df2d448.dip0.t-ipconnect.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
83.220.171.239 attackbotsspam
Unauthorized connection attempt detected from IP address 83.220.171.239 to port 2220 [J]
2020-01-25 16:55:38
64.225.46.192 attackbotsspam
Unauthorized connection attempt detected from IP address 64.225.46.192 to port 2220 [J]
2020-01-25 17:17:36
167.71.217.146 attack
Unauthorized connection attempt detected from IP address 167.71.217.146 to port 2220 [J]
2020-01-25 17:12:34
119.84.121.206 attackspam
Jan 25 07:49:36 tuxlinux sshd[3584]: Invalid user avahi from 119.84.121.206 port 59360
Jan 25 07:49:36 tuxlinux sshd[3584]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.84.121.206 
Jan 25 07:49:36 tuxlinux sshd[3584]: Invalid user avahi from 119.84.121.206 port 59360
Jan 25 07:49:36 tuxlinux sshd[3584]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.84.121.206 
Jan 25 07:49:36 tuxlinux sshd[3584]: Invalid user avahi from 119.84.121.206 port 59360
Jan 25 07:49:36 tuxlinux sshd[3584]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.84.121.206 
Jan 25 07:49:38 tuxlinux sshd[3584]: Failed password for invalid user avahi from 119.84.121.206 port 59360 ssh2
...
2020-01-25 17:04:20
5.196.72.11 attack
Jan 25 09:41:51 localhost sshd\[27298\]: Invalid user zqs from 5.196.72.11 port 57668
Jan 25 09:41:51 localhost sshd\[27298\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.196.72.11
Jan 25 09:41:54 localhost sshd\[27298\]: Failed password for invalid user zqs from 5.196.72.11 port 57668 ssh2
2020-01-25 16:46:53
182.254.184.247 attackspam
Jan 25 07:46:25 mout sshd[11359]: Invalid user ghost from 182.254.184.247 port 46242
2020-01-25 17:12:05
62.234.156.221 attackspam
Unauthorized connection attempt detected from IP address 62.234.156.221 to port 2220 [J]
2020-01-25 17:14:03
195.88.184.186 attackspam
unauthorized connection attempt
2020-01-25 16:49:32
78.222.13.216 attackbots
Jan 24 21:35:38 raspberrypi sshd\[2933\]: Failed password for pi from 78.222.13.216 port 51214 ssh2Jan 25 01:17:45 raspberrypi sshd\[8276\]: Failed password for pi from 78.222.13.216 port 50616 ssh2Jan 25 04:51:00 raspberrypi sshd\[12690\]: Failed password for pi from 78.222.13.216 port 49896 ssh2
...
2020-01-25 16:54:02
51.15.61.42 attackbots
Unauthorized connection attempt detected from IP address 51.15.61.42 to port 2220 [J]
2020-01-25 16:58:25
148.70.121.210 attackbots
Invalid user adminweb from 148.70.121.210 port 50874
2020-01-25 16:55:13
92.119.160.36 attack
Jan 25 08:29:15 debian-2gb-nbg1-2 kernel: \[2196629.484386\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=92.119.160.36 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=9285 PROTO=TCP SPT=51555 DPT=7110 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-25 17:04:39
149.56.241.211 attackbots
149.56.241.211 - - \[25/Jan/2020:06:06:07 +0100\] "POST //wp-login.php HTTP/1.0" 200 7427 "https://wpmeetup-muenchen.org//wp-login.php" "Mozilla/5.0 \(Windows NT 10.0\; Win64\; x64\; rv:66.0\) Gecko/20100101 Firefox/66.0"
149.56.241.211 - - \[25/Jan/2020:06:06:08 +0100\] "POST //wp-login.php HTTP/1.0" 200 7427 "https://wpmeetup-muenchen.org//wp-login.php" "Mozilla/5.0 \(Windows NT 10.0\; Win64\; x64\; rv:66.0\) Gecko/20100101 Firefox/66.0"
149.56.241.211 - - \[25/Jan/2020:06:06:09 +0100\] "POST //wp-login.php HTTP/1.0" 200 7427 "https://wpmeetup-muenchen.org//wp-login.php" "Mozilla/5.0 \(Windows NT 10.0\; Win64\; x64\; rv:66.0\) Gecko/20100101 Firefox/66.0"
2020-01-25 16:52:00
103.93.106.179 attackbots
$f2bV_matches
2020-01-25 16:58:55
185.153.196.48 attackbots
firewall-block, port(s): 21/tcp, 2002/tcp, 3331/tcp, 9000/tcp, 33336/tcp, 33387/tcp, 33394/tcp, 33884/tcp, 33992/tcp
2020-01-25 17:01:02

Recently Reported IPs

139.168.67.220 247.26.245.115 227.143.81.224 217.66.28.4
93.227.164.76 245.68.192.62 48.176.91.14 100.202.46.161
24.98.248.205 16.201.10.36 172.168.15.33 122.68.39.112
165.118.168.44 220.34.184.33 225.43.18.145 245.214.142.185
193.113.81.136 225.72.185.229 170.196.251.158 214.28.202.94