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: Netherlands (the)

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

;; QUESTION SECTION:
;145.165.124.67.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 06:03:35 CST 2025
;; MSG SIZE  rcvd: 107
Host info
67.124.165.145.in-addr.arpa domain name pointer 145.165.EARLY-REGISTRATION.of.SURFnet.invalid.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
67.124.165.145.in-addr.arpa	name = 145.165.EARLY-REGISTRATION.of.SURFnet.invalid.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
125.59.173.200 attack
Honeypot attack, port: 5555, PTR: cm125-59-173-200.hkcable.com.hk.
2020-02-02 01:40:15
45.134.179.57 attackspambots
Feb  1 18:25:38 debian-2gb-nbg1-2 kernel: \[2837194.403339\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=45.134.179.57 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=31232 PROTO=TCP SPT=59849 DPT=203 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-02 01:40:57
221.210.211.15 attackbotsspam
49152/tcp 49152/tcp
[2020-02-01]2pkt
2020-02-02 01:54:26
144.91.78.74 attackspam
...
2020-02-02 02:00:30
144.217.91.253 attack
Jan  4 11:36:34 v22018076590370373 sshd[5235]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.91.253 
...
2020-02-02 02:18:54
41.231.56.98 attackbots
Unauthorized connection attempt detected from IP address 41.231.56.98 to port 22 [J]
2020-02-02 01:56:45
103.100.244.7 attackbotsspam
1433/tcp
[2020-02-01]1pkt
2020-02-02 02:03:44
144.217.89.55 attackspam
Unauthorized connection attempt detected from IP address 144.217.89.55 to port 2220 [J]
2020-02-02 02:19:27
144.34.248.219 attack
Unauthorized connection attempt detected from IP address 144.34.248.219 to port 2220 [J]
2020-02-02 02:09:06
172.69.62.124 attack
2083/tcp 2083/tcp 2083/tcp
[2020-02-01]3pkt
2020-02-02 02:01:03
106.12.112.49 attackspam
Feb  1 14:43:31 vpn01 sshd[14309]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.112.49
Feb  1 14:43:32 vpn01 sshd[14309]: Failed password for invalid user ftpuser from 106.12.112.49 port 41088 ssh2
...
2020-02-02 02:24:08
189.235.140.120 attack
Unauthorized connection attempt detected from IP address 189.235.140.120 to port 80 [J]
2020-02-02 02:14:16
144.22.98.225 attack
Unauthorized connection attempt detected from IP address 144.22.98.225 to port 2220 [J]
2020-02-02 02:15:22
144.217.47.174 attack
Unauthorized connection attempt detected from IP address 144.217.47.174 to port 2220 [J]
2020-02-02 02:25:17
103.126.172.6 attackbots
Unauthorized connection attempt detected from IP address 103.126.172.6 to port 2220 [J]
2020-02-02 02:09:40

Recently Reported IPs

199.12.123.43 18.42.73.29 72.132.235.68 97.76.93.58
157.203.66.37 133.58.46.149 128.95.5.103 153.61.233.163
47.5.17.185 164.45.90.229 161.5.4.138 14.169.30.93
200.192.98.154 186.151.92.45 28.87.230.119 234.29.131.184
44.98.4.18 75.67.3.127 89.120.110.176 7.22.28.10