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

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

;; QUESTION SECTION:
;57.38.18.134.			IN	A

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

;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 14 12:01:07 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 134.18.38.57.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 134.18.38.57.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
119.29.114.235 attackbots
(sshd) Failed SSH login from 119.29.114.235 (-): 5 in the last 3600 secs
2019-11-27 01:40:03
103.40.163.221 attackbotsspam
port scan and connect, tcp 1433 (ms-sql-s)
2019-11-27 01:52:54
129.232.170.218 attackspam
#16015 - [129.232.170.218] Error: 550 5.7.1 Forged HELO hostname detected
#16015 - [129.232.170.218] Error: 550 5.7.1 Forged HELO hostname detected
#16015 - [129.232.170.218] Error: 550 5.7.1 Forged HELO hostname detected
#16015 - [129.232.170.218] Error: 550 5.7.1 Forged HELO hostname detected

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=129.232.170.218
2019-11-27 01:41:33
186.135.74.20 attackbotsspam
Nov 26 16:34:12 server5 sshd[488]: User r.r from 186.135.74.20 not allowed because not listed in AllowUsers
Nov 26 16:34:12 server5 sshd[488]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.135.74.20  user=r.r
Nov 26 16:34:14 server5 sshd[488]: Failed password for invalid user r.r from 186.135.74.20 port 49772 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=186.135.74.20
2019-11-27 01:44:10
218.92.0.212 attack
Nov 26 19:06:51 tux-35-217 sshd\[11010\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.212  user=root
Nov 26 19:06:53 tux-35-217 sshd\[11010\]: Failed password for root from 218.92.0.212 port 35978 ssh2
Nov 26 19:06:56 tux-35-217 sshd\[11010\]: Failed password for root from 218.92.0.212 port 35978 ssh2
Nov 26 19:06:59 tux-35-217 sshd\[11010\]: Failed password for root from 218.92.0.212 port 35978 ssh2
...
2019-11-27 02:09:57
78.128.113.123 attackspambots
Nov 26 18:16:28 mail postfix/smtpd[3965]: warning: unknown[78.128.113.123]: SASL PLAIN authentication failed: 
Nov 26 18:26:14 mail postfix/smtpd[8748]: warning: unknown[78.128.113.123]: SASL PLAIN authentication failed: 
Nov 26 18:26:21 mail postfix/smtpd[8593]: warning: unknown[78.128.113.123]: SASL PLAIN authentication failed:
2019-11-27 01:48:41
186.89.224.73 attackbotsspam
Port 1433 Scan
2019-11-27 02:08:23
37.59.119.181 attackbotsspam
Brute force SMTP login attempted.
...
2019-11-27 02:02:46
110.34.28.99 attack
Unauthorised access (Nov 26) SRC=110.34.28.99 LEN=40 PREC=0x20 TTL=240 ID=18407 DF TCP DPT=23 WINDOW=14600 SYN
2019-11-27 01:34:57
218.92.0.178 attackbotsspam
[ssh] SSH attack
2019-11-27 01:50:46
66.108.165.215 attackbots
2019-11-26T07:43:46.846242-07:00 suse-nuc sshd[31283]: Invalid user gmt from 66.108.165.215 port 51528
...
2019-11-27 02:07:46
173.249.60.176 attackspambots
[Tue Nov 26 12:12:54.250226 2019] [:error] [pid 206920] [client 173.249.60.176:61000] [client 173.249.60.176] ModSecurity: Access denied with code 403 (phase 2). Operator GE matched 5 at TX:anomaly_score. [file "/usr/share/modsecurity-crs/rules/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "91"] [id "949110"] [msg "Inbound Anomaly Score Exceeded (Total Score: 8)"] [severity "CRITICAL"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "ws22vmsma01.ufn.edu.br"] [uri "/"] [unique_id "Xd1A9sr8a1doD-H2aymDtwAAAAU"]
...
2019-11-27 01:33:38
189.135.87.216 attackbots
Automatic report - Port Scan Attack
2019-11-27 01:32:11
106.13.57.178 attackspam
2019-11-26T17:52:06.225855shield sshd\[3465\]: Invalid user szilard from 106.13.57.178 port 38040
2019-11-26T17:52:06.228942shield sshd\[3465\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.57.178
2019-11-26T17:52:08.298994shield sshd\[3465\]: Failed password for invalid user szilard from 106.13.57.178 port 38040 ssh2
2019-11-26T17:58:47.854091shield sshd\[5161\]: Invalid user database from 106.13.57.178 port 41674
2019-11-26T17:58:47.858598shield sshd\[5161\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.57.178
2019-11-27 02:11:17
222.186.173.238 attackbotsspam
Nov 26 18:37:22 sd-53420 sshd\[14451\]: User root from 222.186.173.238 not allowed because none of user's groups are listed in AllowGroups
Nov 26 18:37:23 sd-53420 sshd\[14451\]: Failed none for invalid user root from 222.186.173.238 port 40296 ssh2
Nov 26 18:37:23 sd-53420 sshd\[14451\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.238  user=root
Nov 26 18:37:26 sd-53420 sshd\[14451\]: Failed password for invalid user root from 222.186.173.238 port 40296 ssh2
Nov 26 18:37:29 sd-53420 sshd\[14451\]: Failed password for invalid user root from 222.186.173.238 port 40296 ssh2
...
2019-11-27 01:38:46

Recently Reported IPs

190.74.26.172 224.195.114.79 76.15.218.36 17.189.157.235
201.147.222.13 123.40.91.110 17.169.67.220 101.87.83.255
41.71.94.194 187.77.120.88 83.125.44.182 253.218.178.167
113.66.129.255 179.114.162.71 210.31.104.1 250.164.187.55
52.156.66.108 74.122.6.46 153.30.131.239 176.58.63.93