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

;; QUESTION SECTION:
;145.7.49.37.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 07 04:31:37 CST 2025
;; MSG SIZE  rcvd: 104
Host info
37.49.7.145.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:
37.49.7.145.in-addr.arpa	name = static.kpn.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
176.31.162.82 attackbotsspam
Unauthorized connection attempt detected from IP address 176.31.162.82 to port 2220 [J]
2020-01-26 16:24:11
121.165.73.1 attack
Unauthorized connection attempt detected from IP address 121.165.73.1 to port 2220 [J]
2020-01-26 16:46:58
190.66.3.92 attackspambots
Unauthorized connection attempt detected from IP address 190.66.3.92 to port 2220 [J]
2020-01-26 16:48:47
128.14.134.170 attack
Unauthorized connection attempt detected from IP address 128.14.134.170 to port 21 [J]
2020-01-26 16:53:42
36.155.112.131 attackbotsspam
Unauthorized connection attempt detected from IP address 36.155.112.131 to port 2220 [J]
2020-01-26 16:44:18
49.233.139.79 attackbotsspam
Unauthorized connection attempt detected from IP address 49.233.139.79 to port 2220 [J]
2020-01-26 16:56:56
68.183.153.82 attackbots
Unauthorized connection attempt detected from IP address 68.183.153.82 to port 2220 [J]
2020-01-26 16:29:05
111.231.109.151 attack
Unauthorized connection attempt detected from IP address 111.231.109.151 to port 2220 [J]
2020-01-26 17:05:40
121.66.35.37 attack
Jan 26 09:58:55 journals dovecot: pop3-login: Aborted login \(auth failed, 1 attempts in 4 secs\): user=\, method=PLAIN, rip=121.66.35.37, lip=212.111.212.230, session=\
Jan 26 09:59:04 journals dovecot: pop3-login: Aborted login \(auth failed, 1 attempts in 7 secs\): user=\, method=PLAIN, rip=121.66.35.37, lip=212.111.212.230, session=\
Jan 26 09:59:18 journals dovecot: pop3-login: Aborted login \(auth failed, 1 attempts in 12 secs\): user=\, method=PLAIN, rip=121.66.35.37, lip=212.111.212.230, session=\
Jan 26 10:07:54 journals dovecot: pop3-login: Aborted login \(auth failed, 1 attempts in 4 secs\): user=\, method=PLAIN, rip=121.66.35.37, lip=212.111.212.230, session=\
Jan 26 10:08:04 journals dovecot: pop3-login: Aborted login \(auth failed, 1 attempts in 8 secs\): user=\, method=PLAIN, rip=121.66.35.37, lip=212.111.212.230, s
...
2020-01-26 16:42:18
61.177.172.128 attack
$f2bV_matches
2020-01-26 16:40:27
207.200.8.182 attackbotsspam
Automated report (2020-01-26T06:59:12+00:00). Misbehaving bot detected at this address.
2020-01-26 16:58:07
175.24.42.187 attackspambots
Jan 25 18:46:00 php1 sshd\[18635\]: Invalid user ronald from 175.24.42.187
Jan 25 18:46:00 php1 sshd\[18635\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.24.42.187
Jan 25 18:46:02 php1 sshd\[18635\]: Failed password for invalid user ronald from 175.24.42.187 port 51050 ssh2
Jan 25 18:47:47 php1 sshd\[18853\]: Invalid user redis2 from 175.24.42.187
Jan 25 18:47:47 php1 sshd\[18853\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.24.42.187
2020-01-26 16:46:05
34.95.131.187 attackspambots
Unauthorized connection attempt detected from IP address 34.95.131.187 to port 2220 [J]
2020-01-26 16:51:53
198.98.60.164 attack
Lines containing failures of 198.98.60.164
Jan 23 13:57:28 sanyalnet-cloud-vps sshd[8547]: Connection from 198.98.60.164 port 54488 on 104.167.106.93 port 22
Jan 23 13:57:28 sanyalnet-cloud-vps sshd[8547]: Invalid user support from 198.98.60.164 port 54488
Jan 23 13:57:28 sanyalnet-cloud-vps sshd[8547]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.98.60.164
Jan 23 13:57:31 sanyalnet-cloud-vps sshd[8547]: Failed password for invalid user support from 198.98.60.164 port 54488 ssh2
Jan 23 13:57:31 sanyalnet-cloud-vps sshd[8547]: Connection reset by 198.98.60.164 port 54488 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=198.98.60.164
2020-01-26 16:58:34
124.123.28.43 attackbotsspam
1580014140 - 01/26/2020 05:49:00 Host: 124.123.28.43/124.123.28.43 Port: 445 TCP Blocked
2020-01-26 16:35:19

Recently Reported IPs

83.216.54.47 19.117.71.195 103.196.250.228 41.26.253.74
131.7.247.48 219.6.123.70 43.90.207.160 226.188.231.62
72.253.18.205 15.135.174.89 195.180.49.145 9.246.30.93
134.44.80.79 172.102.236.93 174.174.243.114 155.42.138.41
210.52.236.165 252.8.238.15 187.220.225.194 47.231.69.99