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

;; QUESTION SECTION:
;145.200.190.213.		IN	A

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

;; Query time: 32 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 09 23:42:26 CST 2025
;; MSG SIZE  rcvd: 108
Host info
213.190.200.145.in-addr.arpa domain name pointer 145.200.EARLY-REGISTRATION.of.SURFnet.invalid.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
45.55.233.213 attackbots
Unauthorized connection attempt detected from IP address 45.55.233.213 to port 2220 [J]
2020-01-19 00:45:43
188.149.155.92 attackbots
Invalid user temp from 188.149.155.92 port 38638
2020-01-19 00:26:06
180.76.148.87 attackspam
Invalid user mk from 180.76.148.87 port 59523
2020-01-19 00:27:41
165.22.112.87 attackbotsspam
Jan 18 11:44:33 ny01 sshd[20231]: Failed password for root from 165.22.112.87 port 44730 ssh2
Jan 18 11:47:45 ny01 sshd[20585]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.112.87
Jan 18 11:47:48 ny01 sshd[20585]: Failed password for invalid user youn from 165.22.112.87 port 46306 ssh2
2020-01-19 00:57:55
163.172.39.84 attackbots
Unauthorized connection attempt detected from IP address 163.172.39.84 to port 2220 [J]
2020-01-19 00:58:27
193.112.220.76 attack
Unauthorized connection attempt detected from IP address 193.112.220.76 to port 2220 [J]
2020-01-19 00:24:45
90.188.253.255 attackspambots
Invalid user teo from 90.188.253.255 port 35526
2020-01-19 00:41:55
179.104.28.12 attack
Invalid user admin from 179.104.28.12 port 53068
2020-01-19 00:55:29
187.23.211.32 attack
Invalid user eric from 187.23.211.32 port 49852
2020-01-19 00:53:36
185.249.198.46 attackspambots
Invalid user kathy from 185.249.198.46 port 38074
2020-01-19 00:27:17
116.105.221.111 attackbotsspam
20/1/18@07:59:22: FAIL: Alarm-Network address from=116.105.221.111
20/1/18@07:59:22: FAIL: Alarm-Network address from=116.105.221.111
...
2020-01-19 00:33:53
139.199.112.85 attackbots
Unauthorized connection attempt detected from IP address 139.199.112.85 to port 2220 [J]
2020-01-19 01:02:36
181.48.29.35 attackspam
Unauthorized connection attempt detected from IP address 181.48.29.35 to port 2220 [J]
2020-01-19 00:55:09
178.62.0.215 attackspam
Unauthorized connection attempt detected from IP address 178.62.0.215 to port 2220 [J]
2020-01-19 00:56:49
106.13.67.90 attackspam
Unauthorized connection attempt detected from IP address 106.13.67.90 to port 2220 [J]
2020-01-19 00:37:02

Recently Reported IPs

192.146.126.50 211.99.132.225 169.248.50.22 166.3.136.234
123.196.23.70 178.41.103.115 214.104.235.20 231.191.180.10
224.37.71.227 184.193.27.5 232.176.3.209 189.107.86.157
231.65.135.47 49.27.96.124 74.93.10.179 13.121.12.58
230.157.181.79 104.104.131.83 34.26.19.102 126.26.77.80