Skip to main content
CIDR
/22 · 1.0K IPs
ASN
Netrouting B.V.
Reverse DNS
amsterdam
Last scanned 18 hr ago
Blocklisted
Checking…
Scanning blocklists

Reputation · trust score

A transparent 0–100 signal. Every entity starts at a neutral baseline of 65; threat-intel blocklists, exposure, reverse-DNS, routing and allocation each adjust it up or down. Higher is more trustworthy.

78/100
Moderate
How this score is built

Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →

DNS records

Reverse DNS (PTR)
amsterdam
Forward-confirmed (FCrDNS)
✗ Mismatch
PTR TTL
14400 s
Reverse DNS last checked
2026-09-20 07:55 UTC
Forward DNS last checked
2026-09-20 07:55 UTC

Forward DNS records for amsterdam

TypeValuePriorityTTL
NS ns1.dns.amsterdam
NS ns3.dns.amsterdam
NS ns4.dns.amsterdam
TXT amsterdam zone update: 2026-05-18 16:02:01 +0000 (EPOCH 1779120121) 1800s
TXT amsterdam zone update: 2026-06-11 11:02:01 +0000 (EPOCH 1781175721)
TXT amsterdam zone update: 2026-06-11 13:32:01 +0000 (EPOCH 1781184721)
TXT amsterdam zone update: 2026-06-12 11:02:01 +0000 (EPOCH 1781262121)
TXT amsterdam zone update: 2026-06-12 15:32:02 +0000 (EPOCH 1781278322)
TXT amsterdam zone update: 2026-06-13 01:02:01 +0000 (EPOCH 1781312521)
TXT amsterdam zone update: 2026-06-13 15:02:01 +0000 (EPOCH 1781362921)
TXT amsterdam zone update: 2026-06-14 01:02:01 +0000 (EPOCH 1781398921)
TXT amsterdam zone update: 2026-06-15 04:32:01 +0000 (EPOCH 1781497921)
TXT amsterdam zone update: 2026-06-15 13:02:01 +0000 (EPOCH 1781528521)
TXT amsterdam zone update: 2026-06-16 06:02:01 +0000 (EPOCH 1781589721)
TXT amsterdam zone update: 2026-06-19 15:02:01 +0000 (EPOCH 1781881321)
TXT amsterdam zone update: 2026-06-21 12:02:01 +0000 (EPOCH 1782043321)
TXT amsterdam zone update: 2026-06-22 16:32:01 +0000 (EPOCH 1782145921)
TXT amsterdam zone update: 2026-06-22 18:32:01 +0000 (EPOCH 1782153121)
TXT amsterdam zone update: 2026-06-24 18:32:01 +0000 (EPOCH 1782325921)
TXT amsterdam zone update: 2026-06-25 17:32:02 +0000 (EPOCH 1782408722)
TXT amsterdam zone update: 2026-06-26 00:02:01 +0000 (EPOCH 1782432121)
TXT amsterdam zone update: 2026-06-28 19:02:01 +0000 (EPOCH 1782673321)
TXT amsterdam zone update: 2026-06-28 23:02:01 +0000 (EPOCH 1782687721)
TXT amsterdam zone update: 2026-06-30 01:02:01 +0000 (EPOCH 1782781321)
TXT amsterdam zone update: 2026-07-01 19:32:01 +0000 (EPOCH 1782934321)
TXT amsterdam zone update: 2026-07-04 04:02:01 +0000 (EPOCH 1783137721)
TXT amsterdam zone update: 2026-07-04 20:32:01 +0000 (EPOCH 1783197121)
TXT amsterdam zone update: 2026-07-08 04:32:01 +0000 (EPOCH 1783485121)
TXT amsterdam zone update: 2026-07-09 12:32:01 +0000 (EPOCH 1783600321)
TXT amsterdam zone update: 2026-07-09 16:32:01 +0000 (EPOCH 1783614721)

Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.

Network Allocation for 37.46.193.123

CIDR range
37.46.192.0/22
IP range (int)
623,820,800 — 623,821,823
Prefix length
/22
Organization
Netrouting B.V.
ASN
AS6206
ASN name
Netrouting B.V.
Location
Amsterdam, North Holland, The Netherlands
Coordinates
52.352000, 4.939200
Accuracy radius
20 km
Postal code
1098
Regional Internet Registry
RIPE
Allocated
2012-01-13
Data source(s)
maxmind_city, maxmind_country, ipinfo_lite, maxmind_asn
Last updated
2026-09-19 05:20:44

Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.

Announced prefix
Origin AS
Announcement samples
27,981
Last seen
2026-09-20 19:44:52

Frequently Asked Questions

Who owns 37.46.193.123?

37.46.193.123 is allocated to Netrouting B.V. (AS6206), registered in Amsterdam, The Netherlands.

Where is 37.46.193.123 located?

The geolocation for 37.46.193.123 maps to Amsterdam, The Netherlands based on MaxMind GeoLite2 data. Accuracy depends on the provider and may represent the ISP's regional hub rather than the exact endpoint.

What network is 37.46.193.123 on?

37.46.193.123 belongs to the 37.46.192.0/22 network block announced by AS6206. This range contains 1,024 addresses.

Does 37.46.193.123 have a reverse DNS record?

Reverse DNS (PTR) records are resolved live when you visit this page. If a PTR record exists, it appears in the Reverse DNS field above. PTR records map IP addresses back to hostnames and are commonly used for email authentication and network diagnostics.

Neighbors

Other addresses in the same /24.

Related

Last updated: 2026-09-20 01:47:37 UTC
Share