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

;; QUESTION SECTION:
;145.216.18.30.			IN	A

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

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 15:10:59 CST 2025
;; MSG SIZE  rcvd: 106
Host info
30.18.216.145.in-addr.arpa domain name pointer 145.216.EARLY-REGISTRATION.of.SURFnet.invalid.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
42.117.24.21 attackbotsspam
Unauthorized connection attempt detected from IP address 42.117.24.21 to port 23
2020-01-02 21:01:11
78.109.137.121 attackspam
Unauthorized connection attempt detected from IP address 78.109.137.121 to port 80
2020-01-02 20:59:25
181.49.132.18 attack
Jan  2 08:29:22 zeus sshd[30531]: Failed password for mysql from 181.49.132.18 port 48102 ssh2
Jan  2 08:32:34 zeus sshd[30731]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.49.132.18 
Jan  2 08:32:36 zeus sshd[30731]: Failed password for invalid user dapper from 181.49.132.18 port 47424 ssh2
Jan  2 08:35:45 zeus sshd[30869]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.49.132.18
2020-01-02 20:41:42
91.225.79.162 attack
Unauthorized connection attempt detected from IP address 91.225.79.162 to port 23
2020-01-02 20:23:37
119.120.76.171 attackbotsspam
Unauthorized connection attempt detected from IP address 119.120.76.171 to port 5555
2020-01-02 20:57:28
183.81.105.146 attackbots
Unauthorized connection attempt detected from IP address 183.81.105.146 to port 23
2020-01-02 20:40:45
49.49.245.71 attackbots
Unauthorized connection attempt detected from IP address 49.49.245.71 to port 445
2020-01-02 20:50:45
123.59.148.35 attackspambots
Unauthorized connection attempt detected from IP address 123.59.148.35 to port 23
2020-01-02 20:31:21
42.113.95.121 attackbotsspam
Unauthorized connection attempt detected from IP address 42.113.95.121 to port 23
2020-01-02 21:01:34
117.157.15.27 attackspambots
firewall-block, port(s): 1433/tcp, 6379/tcp, 6380/tcp, 7002/tcp, 8088/tcp
2020-01-02 20:46:16
119.123.220.231 attack
Unauthorized connection attempt detected from IP address 119.123.220.231 to port 445
2020-01-02 20:57:08
222.73.136.205 attackbots
Unauthorized connection attempt detected from IP address 222.73.136.205 to port 445
2020-01-02 20:27:52
113.108.130.157 attackbots
Unauthorized connection attempt detected from IP address 113.108.130.157 to port 1433
2020-01-02 20:32:12
223.152.200.122 attackbotsspam
Unauthorized connection attempt detected from IP address 223.152.200.122 to port 81
2020-01-02 20:53:44
156.235.192.218 attackspam
Unauthorized connection attempt detected from IP address 156.235.192.218 to port 9200
2020-01-02 20:29:47

Recently Reported IPs

34.182.200.134 187.3.161.53 91.34.167.173 86.228.213.132
14.223.81.177 34.103.179.162 217.64.208.47 52.189.173.186
255.114.252.152 6.180.252.64 126.115.100.146 48.60.1.130
92.36.233.185 138.52.55.230 60.46.203.235 103.41.94.120
124.144.54.206 145.51.215.82 128.101.16.245 50.90.46.29