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: The Netherlands

Internet Service Provider: KPN

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

;; QUESTION SECTION:
;194.120.13.138.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 19:37:02 CST 2025
;; MSG SIZE  rcvd: 107
Host info
138.13.120.194.in-addr.arpa domain name pointer static.kpn.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
138.13.120.194.in-addr.arpa	name = static.kpn.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
185.25.51.215 attackbotsspam
Jan 12 13:08:11 vlre-nyc-1 sshd\[26512\]: Invalid user postgres from 185.25.51.215
Jan 12 13:08:11 vlre-nyc-1 sshd\[26512\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.25.51.215
Jan 12 13:08:12 vlre-nyc-1 sshd\[26512\]: Failed password for invalid user postgres from 185.25.51.215 port 37748 ssh2
Jan 12 13:13:11 vlre-nyc-1 sshd\[26575\]: Invalid user vivek from 185.25.51.215
Jan 12 13:13:11 vlre-nyc-1 sshd\[26575\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.25.51.215
...
2020-01-12 21:40:38
165.227.211.13 attack
Unauthorized connection attempt detected from IP address 165.227.211.13 to port 2220 [J]
2020-01-12 21:43:35
114.35.179.124 attackspam
Unauthorized connection attempt detected from IP address 114.35.179.124 to port 4567 [J]
2020-01-12 22:13:30
145.236.80.82 attack
Unauthorized connection attempt detected from IP address 145.236.80.82 to port 23 [J]
2020-01-12 22:11:24
114.32.52.174 attackspam
Unauthorized connection attempt detected from IP address 114.32.52.174 to port 82 [J]
2020-01-12 21:47:19
64.66.29.16 attackspambots
Unauthorized connection attempt detected from IP address 64.66.29.16 to port 23 [J]
2020-01-12 21:56:19
156.218.210.134 attackbotsspam
Unauthorized connection attempt detected from IP address 156.218.210.134 to port 23 [J]
2020-01-12 22:09:23
86.43.127.154 attackspam
Unauthorized connection attempt detected from IP address 86.43.127.154 to port 88 [J]
2020-01-12 21:52:50
110.175.39.110 attackbotsspam
Unauthorized connection attempt detected from IP address 110.175.39.110 to port 81 [J]
2020-01-12 21:48:15
47.39.108.114 attackbotsspam
Unauthorized connection attempt detected from IP address 47.39.108.114 to port 81 [J]
2020-01-12 22:20:56
82.119.119.34 attack
Unauthorized connection attempt detected from IP address 82.119.119.34 to port 5000 [J]
2020-01-12 21:53:43
120.204.86.151 attack
Unauthorized connection attempt detected from IP address 120.204.86.151 to port 23 [J]
2020-01-12 21:46:40
2.135.132.236 attackspambots
Unauthorized connection attempt detected from IP address 2.135.132.236 to port 23 [J]
2020-01-12 22:01:04
58.176.188.151 attack
Unauthorized connection attempt detected from IP address 58.176.188.151 to port 23 [J]
2020-01-12 21:57:20
5.152.110.187 attack
Unauthorized connection attempt detected from IP address 5.152.110.187 to port 2323 [J]
2020-01-12 22:24:11

Recently Reported IPs

139.214.54.5 85.241.178.91 34.3.236.84 5.202.209.113
167.27.0.223 222.51.33.179 82.229.89.45 212.194.156.41
69.22.184.232 146.31.55.75 140.91.148.19 122.92.242.116
67.27.53.4 240.72.239.127 248.87.171.156 168.206.211.56
69.190.220.80 26.255.116.255 231.132.188.66 177.46.97.64