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: Amsterdam

Region: Noord Holland

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:
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#


NetRange:       146.19.10.0 - 146.19.255.255
CIDR:           146.19.12.0/22, 146.19.10.0/23, 146.19.16.0/20, 146.19.64.0/18, 146.19.32.0/19, 146.19.128.0/17
NetName:        RIPE-ERX-146-19-0-0
NetHandle:      NET-146-19-10-0-1
Parent:         NET146 (NET-146-0-0-0-0)
NetType:        Early Registrations, Transferred to RIPE NCC
OriginAS:       
Organization:   RIPE Network Coordination Centre (RIPE)
RegDate:        2004-02-04
Updated:        2026-03-23
Comment:        These addresses have been further assigned to users in the RIPE NCC region. Please note that the organization and point of contact details listed below are those of the RIPE NCC not the current address holder. ** You can find user contact information for the current address holder in the RIPE database at http://www.ripe.net/whois.
Ref:            https://rdap.arin.net/registry/ip/146.19.10.0

ResourceLink:  https://apps.db.ripe.net/db-web-ui/query
ResourceLink:  whois.ripe.net


OrgName:        RIPE Network Coordination Centre
OrgId:          RIPE
Address:        P.O. Box 10096
City:           Amsterdam
StateProv:      
PostalCode:     1001EB
Country:        NL
RegDate:        
Updated:        2013-07-29
Ref:            https://rdap.arin.net/registry/entity/RIPE

ReferralServer:  whois.ripe.net
ResourceLink:  https://apps.db.ripe.net/db-web-ui/query

OrgTechHandle: RNO29-ARIN
OrgTechName:   RIPE NCC Operations
OrgTechPhone:  +31 20 535 4444 
OrgTechEmail:  hostmaster@ripe.net
OrgTechRef:    https://rdap.arin.net/registry/entity/RNO29-ARIN

OrgAbuseHandle: ABUSE3850-ARIN
OrgAbuseName:   Abuse Contact
OrgAbusePhone:  +31205354444 
OrgAbuseEmail:  abuse@ripe.net
OrgAbuseRef:    https://rdap.arin.net/registry/entity/ABUSE3850-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 146.19.254.157
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63985
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;146.19.254.157.			IN	A

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

;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Oct 18 06:30:20 CST 2026
;; MSG SIZE  rcvd: 107
Host info
Host 157.254.19.146.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 157.254.19.146.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
167.179.76.246 attack
06.10.2019 04:34:46 Recursive DNS scan
2019-10-06 16:39:57
14.0.19.6 attack
10/05/2019-23:48:15.614930 14.0.19.6 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-10-06 16:46:31
118.89.35.168 attack
Oct  6 08:32:26 lnxded64 sshd[4965]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.89.35.168
2019-10-06 16:51:19
2001:bc8:6005:1a:598c:affe:c854:da29 attackbotsspam
LGS,WP GET /wp-login.php
GET /blog/wp-login.php
GET /wordpress/wp-login.php
2019-10-06 16:43:11
186.201.214.163 attackspambots
$f2bV_matches
2019-10-06 16:36:30
78.133.136.142 attack
Oct  6 08:29:17 v22018076622670303 sshd\[20933\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=78.133.136.142  user=root
Oct  6 08:29:19 v22018076622670303 sshd\[20933\]: Failed password for root from 78.133.136.142 port 54084 ssh2
Oct  6 08:33:11 v22018076622670303 sshd\[20964\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=78.133.136.142  user=root
...
2019-10-06 16:17:36
197.225.166.204 attack
[Aegis] @ 2019-10-06 09:09:36  0100 -> Multiple authentication failures.
2019-10-06 16:53:09
140.143.236.227 attack
$f2bV_matches
2019-10-06 16:41:33
106.225.129.108 attackspam
Oct  5 22:14:27 sachi sshd\[24447\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.225.129.108  user=root
Oct  5 22:14:29 sachi sshd\[24447\]: Failed password for root from 106.225.129.108 port 49575 ssh2
Oct  5 22:19:38 sachi sshd\[24871\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.225.129.108  user=root
Oct  5 22:19:41 sachi sshd\[24871\]: Failed password for root from 106.225.129.108 port 39025 ssh2
Oct  5 22:24:16 sachi sshd\[25272\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.225.129.108  user=root
2019-10-06 16:58:58
128.199.137.252 attackbots
Oct  6 11:14:51 server sshd\[24920\]: User root from 128.199.137.252 not allowed because listed in DenyUsers
Oct  6 11:14:51 server sshd\[24920\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.137.252  user=root
Oct  6 11:14:53 server sshd\[24920\]: Failed password for invalid user root from 128.199.137.252 port 49620 ssh2
Oct  6 11:20:38 server sshd\[22812\]: User root from 128.199.137.252 not allowed because listed in DenyUsers
Oct  6 11:20:38 server sshd\[22812\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.137.252  user=root
2019-10-06 16:21:25
54.39.51.31 attack
Invalid user lpadm from 54.39.51.31 port 34610
2019-10-06 16:39:12
201.55.126.57 attackbots
ssh failed login
2019-10-06 16:28:40
210.57.22.204 attackbots
Oct  5 17:43:24 hanapaa sshd\[28655\]: Invalid user Pa55w0rd@2019 from 210.57.22.204
Oct  5 17:43:24 hanapaa sshd\[28655\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.57.22.204
Oct  5 17:43:26 hanapaa sshd\[28655\]: Failed password for invalid user Pa55w0rd@2019 from 210.57.22.204 port 21731 ssh2
Oct  5 17:48:24 hanapaa sshd\[29062\]: Invalid user Test@2019 from 210.57.22.204
Oct  5 17:48:24 hanapaa sshd\[29062\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.57.22.204
2019-10-06 16:40:55
103.233.76.254 attack
2019-10-06T05:50:22.161566abusebot-5.cloudsearch.cf sshd\[7437\]: Invalid user arma2 from 103.233.76.254 port 40780
2019-10-06 16:53:55
62.219.160.251 attackbotsspam
Automatic report - Port Scan Attack
2019-10-06 16:19:38

Recently Reported IPs

48.46.5.97 77.67.26.84 64.205.72.8 64.205.72.74
64.205.72.59 64.205.72.122 200.138.46.79 218.56.101.190
20.29.59.15 103.135.33.203 103.135.33.252 190.121.53.245
95.104.184.45 45.234.212.72 52.248.43.126 14.212.85.141
48.217.233.95 124.123.44.65 20.29.44.88