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: Bad Zwischenahn

Region: Niedersachsen

Country: Germany

Internet Service Provider: Telekom

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

;; QUESTION SECTION:
;93.225.49.64.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 27 08:21:43 CST 2025
;; MSG SIZE  rcvd: 105
Host info
64.49.225.93.in-addr.arpa domain name pointer p5de13140.dip0.t-ipconnect.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
64.49.225.93.in-addr.arpa	name = p5de13140.dip0.t-ipconnect.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
69.119.114.36 attackspambots
$f2bV_matches
2020-04-20 12:45:14
193.56.28.161 attackbots
scan z
2020-04-20 12:46:22
14.120.183.217 attack
Port probing on unauthorized port 23
2020-04-20 13:13:26
208.91.109.18 attackbots
" "
2020-04-20 12:36:06
109.128.208.180 attackbotsspam
Unauthorized connection attempt detected from IP address 109.128.208.180 to port 23
2020-04-20 12:38:09
52.68.122.160 attackbotsspam
Apr 20 07:53:05 hosting sshd[20000]: Invalid user daijiabao from 52.68.122.160 port 42512
...
2020-04-20 13:11:29
222.186.52.139 attackbots
Unauthorized connection attempt detected from IP address 222.186.52.139 to port 22
2020-04-20 12:56:27
212.83.181.143 attackbots
Trying ports that it shouldn't be.
2020-04-20 12:44:12
80.82.64.73 attackbotsspam
04/20/2020-01:02:00.621859 80.82.64.73 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-04-20 13:15:14
110.77.246.68 attackbots
Unauthorised access (Apr 20) SRC=110.77.246.68 LEN=52 TTL=114 ID=13119 DF TCP DPT=445 WINDOW=8192 SYN
2020-04-20 12:53:29
129.28.18.88 attackbots
Apr 20 03:59:00 scw-6657dc sshd[17325]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.28.18.88  user=root
Apr 20 03:59:00 scw-6657dc sshd[17325]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.28.18.88  user=root
Apr 20 03:59:02 scw-6657dc sshd[17325]: Failed password for root from 129.28.18.88 port 48230 ssh2
...
2020-04-20 13:06:25
123.232.96.2 attackspam
SSH-bruteforce attempts
2020-04-20 12:49:14
128.199.212.82 attackbots
T: f2b ssh aggressive 3x
2020-04-20 12:52:53
96.9.70.234 attack
Apr 20 05:58:52 tuxlinux sshd[62376]: Invalid user co from 96.9.70.234 port 44224
Apr 20 05:58:52 tuxlinux sshd[62376]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.9.70.234 
Apr 20 05:58:52 tuxlinux sshd[62376]: Invalid user co from 96.9.70.234 port 44224
Apr 20 05:58:52 tuxlinux sshd[62376]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.9.70.234 
...
2020-04-20 13:14:02
106.12.173.149 attack
Apr 20 06:33:09 haigwepa sshd[30313]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.173.149 
Apr 20 06:33:12 haigwepa sshd[30313]: Failed password for invalid user jm from 106.12.173.149 port 34788 ssh2
...
2020-04-20 12:47:43

Recently Reported IPs

71.250.90.147 155.157.93.94 161.205.171.146 195.188.223.67
182.215.37.228 133.173.31.20 5.39.243.74 139.238.59.68
53.94.250.153 143.171.119.220 16.115.121.233 47.55.248.96
145.138.112.158 72.158.164.15 223.43.223.49 116.148.12.238
118.175.77.136 37.35.41.90 195.72.39.59 204.216.98.70