Domain report: megagadgets.nl

Registration

info

.nl country-code

Found

TLD: .nl (country-code)
ICANN policies apply: no

Lookup error: https://rdap.sidn.nl/domain/megagadgets.nl returned HTTP 429

Checks

i

.nl is a country-code TLD (ccTLD)

Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.

#1
✓ TLD delegated and signed #2

.nl is delegated in the root zone and DNSSEC-signed.
i

Could not be checked

The RDAP lookup failed, so this could not be checked: https://rdap.sidn.nl/domain/megagadgets.nl returned HTTP 429

#3

Delegation

warn

ns1.hypernode.com, ns2.hypernode.com, ns3.hypernode.com

Found

Parent zone: nl
Delegation from: ns1.dns.nl (194.0.28.53)
NS at the parent: ns1.hypernode.com, ns2.hypernode.com, ns3.hypernode.com
NS in the zone: ns1.hypernode.com, ns2.hypernode.com, ns3.hypernode.com

Nameserver	Addresses	Network (AS)	Glue
ns1.hypernode.com	80.84.227.137	AS31586 AS-TBNLTN - Signet B.V., NL	-
ns2.hypernode.com	18.196.180.73	AS16509 AMAZON-02 - Amazon.com, Inc., US	-
ns3.hypernode.com	34.251.57.20	AS16509 AMAZON-02 - Amazon.com, Inc., US	-

Checks

✓ 3 nameservers #6

Delegated to ns1.hypernode.com, ns2.hypernode.com, ns3.hypernode.com.
✓ Parent and zone agree #7

The parent delegation and the zone's NS records list the same nameservers.
✓ No glue needed #8

All nameservers are outside the zone, so no glue records are needed.
✓ All names resolve #9

Every nameserver name has an address and is not an alias.
✓ Nameservers in different networks #10

The nameservers are spread over 3 IPv4 /24s and 0 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS16509 (AMAZON-02 - Amazon.com, Inc., US): 2 addresses; AS31586 (AS-TBNLTN - Signet B.V., NL): 1 address.
i

All nameserver names under .com

All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.

#12
!

No IPv6

None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

#13

Nameservers

pass

3 of 3 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.hypernode.com 80.84.227.137	NOERROR, 11 ms, authoritative	no	yes / yes	refused	-
ns2.hypernode.com 18.196.180.73	NOERROR, 5 ms, authoritative	no	yes / yes	refused	-
ns3.hypernode.com 34.251.57.20	NOERROR, 23 ms, authoritative	no	yes / yes	refused	-

Checks

✓ All respond #14

All 3 nameserver addresses answered.
✓ All authoritative #15

Every responding nameserver answers authoritatively for the zone.
✓ No recursion #16

The nameservers do not answer recursive queries for other domains.
✓ No version disclosed #17

The nameservers don't reveal their software version.
✓ Zone transfers refused #18

No nameserver allows a zone transfer to the public.
✓ TCP supported #19

All nameservers answer over TCP.
✓ EDNS supported #20

All nameservers support EDNS(0).
✓ Public addresses #21

All nameserver addresses are publicly routable.

SOA

pass

serial 2025121103 · primary ns1.hypernode.com

Found

Primary (MNAME): ns1.hypernode.com
Contact (RNAME): hostmaster.hypernode.com
Serial: 2025121103
Refresh / retry: 10800 s / 3600 s
Expire: 604800 s
Negative TTL: 3600 s

Serial per nameserver

Nameserver	Serial
ns1.hypernode.com (80.84.227.137)	2025121103
ns2.hypernode.com (18.196.180.73)	2025121103
ns3.hypernode.com (34.251.57.20)	2025121103

Checks

✓ Serial 2025121103 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
✓ Primary is a public nameserver #24

The primary nameserver ns1.hypernode.com is one of the listed nameservers.
✓ Contact hostmaster@hypernode.com #25

The SOA RNAME hostmaster.hypernode.com means hostmaster@hypernode.com.
✓ Date-based serial #26

The serial 2025121103 follows the YYYYMMDDnn convention (2025-12-11).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver: no
Denial of existence: NSEC3
NSEC3: 0 iterations, 0-byte salt
Signatures valid until: 5 November 2026

DNSKEY in the zone

Key tag	Role	Algorithm
22357	KSK (257)	RSASHA256 (8)

Checks

!

Signed but not delegated securely

The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.

#27
✓ Modern algorithms #29

Key algorithms: RSASHA256 (8).
✓ Signatures valid until 2026-11-05 #30

The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.
✓ NSEC3 as recommended #31

The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

warn

17 records at the apex

Found

Read from: 80.84.227.137:53

Type	Value	TTL
SOA	ns1.hypernode.com. hostmaster.hypernode.com. 2025121103 10800 3600 604800 3600	600
NS	ns2.hypernode.com.	43200
NS	ns1.hypernode.com.	43200
NS	ns3.hypernode.com.	43200
A	46.21.227.20	60
MX	10 ALT4.ASPMX.L.GOOGLE.COM.	3600
MX	5 ALT2.ASPMX.L.GOOGLE.COM.	3600
MX	10 ALT3.ASPMX.L.GOOGLE.COM.	3600
MX	5 ALT1.ASPMX.L.GOOGLE.COM.	3600
MX	1 ASPMX.L.GOOGLE.COM.	3600
TXT	"google-gws-recovery-domain-verification=42795218"	600
TXT	"v=spf1 mx a include:_spf.mailcampaigns.nl ~all"	600
TXT	"v=DMARC1; p=none; sp=none; rua=mailto:achmed@hypemedia.nl; ruf=mailto:achmed@hypemedia.nl; rf=afrf; pct=100; ri=86400"	600
TXT	"MS=ms96935610"	600
TXT	"megagadgets-nl.mail.protection.outlook.com"	600
TXT	"google-site-verification=V1GwCH8JsUArgK0olo0PmmhKC3FAD5VEhYg91c3Lcm8"	600
TXT	"v=spf1 include:spf.megagadgets.hypernode.io include:sendgrid.net include:spf.protection.outlook.com include:servers.mcsv.net ip4:185.87.249.199 ip4:89.105.218.200 ip4:213.189.0.0/23 ip4:185.99.128.0/22 -all"	600

Checks

!

Very low TTLs

These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 12h; resolvers may use either.

#32
✓ No CNAME at the apex #33

The zone apex has no CNAME record.
✓ No wildcard #34

Names that don't exist return NXDOMAIN.
i

No CAA records

Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.

#35