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

;; QUESTION SECTION:
;193.29.123.139.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 02:43:55 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 139.123.29.193.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 139.123.29.193.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
95.141.199.94 attackbotsspam
[portscan] Port scan
2019-11-07 21:13:31
128.199.80.77 attack
WordPress login Brute force / Web App Attack on client site.
2019-11-07 20:53:28
79.98.53.67 attack
Fail2Ban Ban Triggered
2019-11-07 21:16:20
176.104.107.105 attack
postfix (unknown user, SPF fail or relay access denied)
2019-11-07 21:03:01
209.18.47.61 attackspam
Tried to ddos port 53 on me, and pinged me.
2019-11-07 21:27:39
66.70.188.12 attack
2019-11-07T13:02:36.659763abusebot-6.cloudsearch.cf sshd\[30630\]: Invalid user user from 66.70.188.12 port 39380
2019-11-07 21:13:01
182.236.10.120 attack
Automatic report - XMLRPC Attack
2019-11-07 20:59:05
123.30.168.119 attack
WordPress login Brute force / Web App Attack on client site.
2019-11-07 20:45:34
51.91.108.183 attackspambots
Automatically reported by fail2ban report script (mx1)
2019-11-07 21:20:36
178.33.39.181 attackbotsspam
11/07/2019-07:21:03.849126 178.33.39.181 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-11-07 20:59:32
188.187.162.139 attackbotsspam
Unauthorized SSH login attempts
2019-11-07 21:12:45
183.129.188.92 attackspam
Nov  7 11:50:41 gw1 sshd[18789]: Failed password for root from 183.129.188.92 port 45608 ssh2
...
2019-11-07 20:42:52
213.251.192.18 attackbots
Lines containing failures of 213.251.192.18 (max 1000)
Nov  5 11:55:40 localhost sshd[31394]: Invalid user zoey from 213.251.192.18 port 59966
Nov  5 11:55:40 localhost sshd[31394]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.251.192.18 
Nov  5 11:55:42 localhost sshd[31394]: Failed password for invalid user zoey from 213.251.192.18 port 59966 ssh2
Nov  5 11:55:42 localhost sshd[31394]: Received disconnect from 213.251.192.18 port 59966:11: Bye Bye [preauth]
Nov  5 11:55:42 localhost sshd[31394]: Disconnected from invalid user zoey 213.251.192.18 port 59966 [preauth]
Nov  5 12:17:11 localhost sshd[9162]: User r.r from 213.251.192.18 not allowed because listed in DenyUsers
Nov  5 12:17:11 localhost sshd[9162]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.251.192.18  user=r.r
Nov  5 12:17:13 localhost sshd[9162]: Failed password for invalid user r.r from 213.251.192.18 port 40764........
------------------------------
2019-11-07 20:44:38
113.108.126.2 attackbotsspam
FTP brute-force attack
2019-11-07 21:01:48
200.188.129.178 attackspambots
Triggered by Fail2Ban at Ares web server
2019-11-07 21:23:13

Recently Reported IPs

212.247.144.174 238.18.89.154 218.169.172.127 40.148.148.250
41.118.239.180 160.242.203.18 139.117.209.72 26.233.76.96
3.217.71.26 201.48.50.95 119.3.19.254 91.16.139.5
187.132.65.27 137.120.82.63 107.14.101.159 217.80.128.24
184.55.246.55 32.88.241.109 186.80.3.218 73.101.190.255