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

;; QUESTION SECTION:
;93.229.122.52.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 17 00:44:36 CST 2025
;; MSG SIZE  rcvd: 106
Host info
52.122.229.93.in-addr.arpa domain name pointer p5de57a34.dip0.t-ipconnect.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
52.122.229.93.in-addr.arpa	name = p5de57a34.dip0.t-ipconnect.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.12.209.38 attackspam
Feb  5 04:14:42 server sshd\[2487\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.209.38  user=root
Feb  5 04:14:44 server sshd\[2487\]: Failed password for root from 106.12.209.38 port 44960 ssh2
Feb  5 04:25:43 server sshd\[4888\]: Invalid user matt from 106.12.209.38
Feb  5 04:25:43 server sshd\[4888\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.209.38 
Feb  5 04:25:44 server sshd\[4888\]: Failed password for invalid user matt from 106.12.209.38 port 41296 ssh2
...
2020-02-05 10:32:41
134.249.121.243 attackbots
Unauthorized connection attempt detected from IP address 134.249.121.243 to port 2220 [J]
2020-02-05 10:27:28
51.198.120.72 attackbotsspam
Unauthorized connection attempt detected from IP address 51.198.120.72 to port 23 [J]
2020-02-05 10:15:41
27.120.101.61 attackbots
Automatic report - SSH Brute-Force Attack
2020-02-05 10:19:21
37.131.193.153 attack
Unauthorized connection attempt detected from IP address 37.131.193.153 to port 5555 [J]
2020-02-05 10:44:15
106.12.120.207 attack
Unauthorized connection attempt detected from IP address 106.12.120.207 to port 2220 [J]
2020-02-05 10:33:12
96.64.182.221 attackspambots
Unauthorized connection attempt detected from IP address 96.64.182.221 to port 81 [J]
2020-02-05 10:35:07
158.174.194.9 attackbotsspam
Unauthorized connection attempt detected from IP address 158.174.194.9 to port 5555 [J]
2020-02-05 10:25:45
46.21.69.98 attackspambots
Unauthorized connection attempt detected from IP address 46.21.69.98 to port 8080 [J]
2020-02-05 10:16:55
175.4.222.250 attack
Unauthorized connection attempt detected from IP address 175.4.222.250 to port 23 [J]
2020-02-05 10:24:21
47.100.92.157 attackspambots
Unauthorized connection attempt detected from IP address 47.100.92.157 to port 1433 [J]
2020-02-05 10:42:02
58.214.255.41 attack
Unauthorized connection attempt detected from IP address 58.214.255.41 to port 2220 [J]
2020-02-05 10:15:07
78.163.113.32 attackbots
Unauthorized connection attempt detected from IP address 78.163.113.32 to port 23 [J]
2020-02-05 10:38:15
77.42.85.151 attackbots
Unauthorized connection attempt detected from IP address 77.42.85.151 to port 2323 [J]
2020-02-05 10:13:38
196.21.218.222 attackspambots
Unauthorized connection attempt from IP address 196.21.218.222 on Port 445(SMB)
2020-02-05 10:21:46

Recently Reported IPs

143.74.49.227 2.93.240.199 134.53.17.99 108.111.179.70
32.159.93.31 211.203.75.114 45.143.86.118 90.22.185.207
76.246.220.12 6.180.133.30 166.21.123.86 6.165.109.131
33.118.71.236 91.131.42.94 92.213.45.28 65.200.184.177
35.95.156.237 13.203.165.91 201.52.82.135 154.45.72.52