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

;; QUESTION SECTION:
;37.138.214.254.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 17 05:34:52 CST 2025
;; MSG SIZE  rcvd: 107
Host info
254.214.138.37.in-addr.arpa domain name pointer dyndsl-037-138-214-254.ewe-ip-backbone.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
254.214.138.37.in-addr.arpa	name = dyndsl-037-138-214-254.ewe-ip-backbone.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
92.63.196.10 attackspambots
firewall-block, port(s): 34671/tcp
2020-01-31 22:36:07
52.34.83.11 attackbots
01/31/2020-15:40:47.211740 52.34.83.11 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-31 22:50:57
221.213.75.177 attackspam
Unauthorized connection attempt detected from IP address 221.213.75.177 to port 8118 [J]
2020-01-31 22:39:36
111.40.50.116 attackbotsspam
Jan 31 11:40:23 lock-38 sshd[24972]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.40.50.116 
Jan 31 11:40:25 lock-38 sshd[24972]: Failed password for invalid user udaramati from 111.40.50.116 port 59528 ssh2
...
2020-01-31 22:25:11
167.114.152.139 attackbots
Unauthorized connection attempt detected from IP address 167.114.152.139 to port 2220 [J]
2020-01-31 22:26:08
138.68.20.158 attack
kp-sea2-01 recorded 2 login violations from 138.68.20.158 and was blocked at 2020-01-31 08:43:56. 138.68.20.158 has been blocked on 2 previous occasions. 138.68.20.158's first attempt was recorded at 2019-08-29 02:15:24
2020-01-31 22:32:23
221.13.12.118 attackbots
Unauthorized connection attempt detected from IP address 221.13.12.118 to port 443 [J]
2020-01-31 22:42:35
113.137.36.187 attackspambots
Unauthorized connection attempt detected from IP address 113.137.36.187 to port 2220 [J]
2020-01-31 23:01:30
182.61.44.136 attackspambots
Unauthorized connection attempt detected from IP address 182.61.44.136 to port 2220 [J]
2020-01-31 22:48:52
221.225.83.148 attackspam
Jan 31 14:08:40 game-panel sshd[28354]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.225.83.148
Jan 31 14:08:41 game-panel sshd[28354]: Failed password for invalid user firaki from 221.225.83.148 port 36480 ssh2
Jan 31 14:15:39 game-panel sshd[28894]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.225.83.148
2020-01-31 23:01:53
79.173.157.26 attackbots
TCP Port Scanning
2020-01-31 22:31:52
80.82.77.33 attackbots
port scan and connect, tcp 8080 (http-proxy)
2020-01-31 22:48:35
185.216.140.252 attack
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2020-01-31 22:28:00
121.58.237.227 attackbotsspam
TCP Port Scanning
2020-01-31 22:43:33
104.236.250.88 attackspambots
Invalid user jia from 104.236.250.88 port 43672
2020-01-31 23:07:00

Recently Reported IPs

222.44.131.0 60.69.207.104 208.170.102.240 71.115.221.186
2.61.6.27 116.145.58.194 89.73.8.233 210.178.168.81
25.155.70.198 44.172.25.138 169.171.63.156 155.108.233.44
61.165.173.174 99.83.98.8 162.72.170.65 73.177.181.212
180.255.114.89 4.135.18.123 143.72.222.147 8.182.108.253