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

;; QUESTION SECTION:
;145.154.69.71.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 21 05:17:05 CST 2025
;; MSG SIZE  rcvd: 106
Host info
71.69.154.145.in-addr.arpa domain name pointer 145.154.EARLY-REGISTRATION.of.SURFnet.invalid.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
220.172.249.2 attackspambots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-12 07:49:13
160.124.140.147 attackspam
May 12 01:14:48 legacy sshd[16008]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=160.124.140.147
May 12 01:14:50 legacy sshd[16008]: Failed password for invalid user zabbix from 160.124.140.147 port 48090 ssh2
May 12 01:21:38 legacy sshd[16340]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=160.124.140.147
...
2020-05-12 07:36:21
104.206.128.50 attackbotsspam
May 12 01:23:04 debian-2gb-nbg1-2 kernel: \[11498249.144012\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=104.206.128.50 DST=195.201.40.59 LEN=44 TOS=0x00 PREC=0x00 TTL=239 ID=54321 PROTO=TCP SPT=54713 DPT=1543 WINDOW=65535 RES=0x00 SYN URGP=0
2020-05-12 08:27:03
112.85.42.94 attack
SSH Brute Force
2020-05-12 07:59:55
185.153.180.27 attack
05/11/2020-18:35:00.897198 185.153.180.27 Protocol: 17 ET SCAN Sipvicious User-Agent Detected (friendly-scanner)
2020-05-12 08:22:25
117.48.208.71 attackbots
Invalid user ubuntu from 117.48.208.71 port 52596
2020-05-12 07:41:13
132.145.165.87 attack
$f2bV_matches | Triggered by Fail2Ban at Vostok web server
2020-05-12 07:58:59
111.53.195.115 attack
port scan and connect, tcp 1433 (ms-sql-s)
2020-05-12 08:26:18
164.132.225.151 attack
SSH Brute Force
2020-05-12 07:54:45
49.234.150.207 attackspambots
SSH Brute Force
2020-05-12 07:46:12
77.48.46.241 attackbotsspam
SSH Brute Force
2020-05-12 07:44:42
185.143.223.244 attackspambots
Multiport scan 22 ports : 2289(x3) 3383(x4) 3384(x5) 3385(x6) 3386(x6) 3387(x6) 3388(x19) 3390(x27) 3391(x21) 3392(x18) 3393(x19) 3394(x18) 3395(x7) 3396(x7) 3397(x4) 3398(x4) 3399(x3) 4489(x2) 5589(x2) 6689(x2) 7789(x3) 8889(x3)
2020-05-12 07:53:27
172.96.242.112 attackbots
May 12 06:03:40 webhost01 sshd[805]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.96.242.112
May 12 06:03:42 webhost01 sshd[805]: Failed password for invalid user temp from 172.96.242.112 port 42604 ssh2
...
2020-05-12 07:35:00
188.254.0.2 attackspambots
Invalid user jenkins from 188.254.0.2 port 56496
2020-05-12 07:32:48
218.21.217.122 attackspam
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-12 08:18:40

Recently Reported IPs

88.13.150.5 151.189.157.126 65.50.15.213 4.217.143.102
50.98.202.6 67.14.233.182 123.171.102.158 119.235.89.139
114.8.210.229 76.128.254.82 218.249.215.126 170.162.102.173
76.183.47.225 122.49.74.28 248.41.184.92 187.218.107.108
116.141.131.114 97.155.91.61 135.20.188.251 76.72.3.228