Domain report: rendement.nl

Registration

info

.nl country-code

Found

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

Lookup error: https://rdap.sidn.nl/domain/rendement.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/rendement.nl returned HTTP 429

#3

Delegation

info

ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com

Found

Parent zone: nl
Delegation from: ns1.dns.nl (194.0.28.53)
NS at the parent: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com
NS in the zone: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com

Nameserver	Addresses	Network (AS)	Glue
ns-cloud-d1.googledomains.com	216.239.32.109 2001:4860:4802:32::6d	AS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US	-
ns-cloud-d2.googledomains.com	216.239.34.109 2001:4860:4802:34::6d	AS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US	-
ns-cloud-d3.googledomains.com	216.239.36.109 2001:4860:4802:36::6d	AS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US	-
ns-cloud-d4.googledomains.com	216.239.38.109 2001:4860:4802:38::6d	AS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US	-

Checks

✓ 4 nameservers #6

Delegated to ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.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.
i

One address family in one network

all IPv6 addresses are in 2001:4860:4802::/48, while the other address family is spread over several networks.

#10
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS15169 (GOOGLE - Google LLC, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

#11
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
✓ All reachable over IPv6 #13

Every nameserver has an IPv6 address.

Nameservers

pass

8 of 8 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns-cloud-d1.googledomains.com 216.239.32.109	NOERROR, 12 ms, authoritative	no	yes / yes	refused	-
ns-cloud-d1.googledomains.com 2001:4860:4802:32::6d	NOERROR, 12 ms, authoritative	no	yes / yes	refused	-
ns-cloud-d2.googledomains.com 216.239.34.109	NOERROR, 12 ms, authoritative	no	yes / yes	refused	-
ns-cloud-d2.googledomains.com 2001:4860:4802:34::6d	NOERROR, 12 ms, authoritative	no	yes / yes	refused	-
ns-cloud-d3.googledomains.com 216.239.36.109	NOERROR, 42 ms, authoritative	no	yes / yes	refused	-
ns-cloud-d3.googledomains.com 2001:4860:4802:36::6d	NOERROR, 42 ms, authoritative	no	yes / yes	refused	-
ns-cloud-d4.googledomains.com 216.239.38.109	NOERROR, 11 ms, authoritative	no	yes / yes	refused	-
ns-cloud-d4.googledomains.com 2001:4860:4802:38::6d	NOERROR, 12 ms, authoritative	no	yes / yes	refused	-

Checks

✓ All respond #14

All 8 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

warn

serial 1 · primary ns-cloud-d1.googledomains.com

Found

Primary (MNAME): ns-cloud-d1.googledomains.com
Contact (RNAME): cloud-dns-hostmaster.google.com
Serial: 1
Refresh / retry: 21600 s / 3600 s
Expire: 259200 s
Negative TTL: 300 s

Serial per nameserver

Nameserver	Serial
ns-cloud-d1.googledomains.com (216.239.32.109)	1
ns-cloud-d1.googledomains.com (2001:4860:4802:32::6d)	1
ns-cloud-d2.googledomains.com (216.239.34.109)	1
ns-cloud-d2.googledomains.com (2001:4860:4802:34::6d)	1
ns-cloud-d3.googledomains.com (216.239.36.109)	1
ns-cloud-d3.googledomains.com (2001:4860:4802:36::6d)	1
ns-cloud-d4.googledomains.com (216.239.38.109)	1
ns-cloud-d4.googledomains.com (2001:4860:4802:38::6d)	1

Checks

✓ Serial 1 everywhere #22

All nameservers serve the same version of the zone.
!

Unusual SOA timers

expire 3d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 6h, retry 1h, expire 3d, negative TTL 5m.

#23
✓ Primary is a public nameserver #24

The primary nameserver ns-cloud-d1.googledomains.com is one of the listed nameservers.
✓ Contact cloud-dns-hostmaster@google.com #25

The SOA RNAME cloud-dns-hostmaster.google.com means cloud-dns-hostmaster@google.com.
✓ Counter serial #26

The serial 1 is a plain counter.

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC3
NSEC3: 1 iterations, 8-byte salt
Signatures valid until: 10 November 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
31504	RSASHA256 (8)	SHA256 5FE9DF4982A0A5FD…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
31504	KSK (257)	RSASHA256 (8)
53596	ZSK (256)	RSASHA256 (8)

Checks

✓ Signed and validated #27

The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
✓ DS matches a key #28

The DS record at the parent matches a key in the zone: key tag 31504 (SHA256).
✓ Modern algorithms #29

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

The earliest DNSKEY/SOA signature expires at 2026-11-10 04:02 UTC.
!

NSEC3 with extra iterations or salt

NSEC3 uses 1 iteration and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.

#31

Records

info

17 records at the apex

Found

Read from: 216.239.32.109:53

Type	Value	TTL
SOA	ns-cloud-d1.googledomains.com. cloud-dns-hostmaster.google.com. 1 21600 3600 259200 300	21600
NS	ns-cloud-d2.googledomains.com.	21600
NS	ns-cloud-d4.googledomains.com.	21600
NS	ns-cloud-d1.googledomains.com.	21600
NS	ns-cloud-d3.googledomains.com.	21600
A	136.144.179.83	900
MX	10 de-smtp-inbound-2.mimecast.com.	300
MX	10 de-smtp-inbound-1.mimecast.com.	300
TXT	"google-site-verification=uxwb_b-QsKFSO_Y2QSWlbN5D6T_6VBucjzVKOtCZ-Qs"	900
TXT	"0ed1fe018ab5e08fc3b6df418bbd436be7029e1386"	900
TXT	"google-site-verification=LkX7vxWJkWdEXDd39_xmozElZlS0f18tIE08phjAKXQ"	900
TXT	"google-site-verification=6JzGpK5L0nBEyvl_TlyexKaUi4P2syY2EL44dCsRYks"	900
TXT	"MS=ms69402614"	900
TXT	"adobe-idp-site-verification=e7d316e26179ad0d4b3f90cf2a0754eec7efe5ffd4e42fd68fb1bf562238e1e5"	900
TXT	"MS=ms31741119"	900
TXT	"docusign=7f7fc8e8-9a9f-4523-82cb-ab2d7ee2526c"	900
TXT	"v=spf1 include:de._netblocks.mimecast.com include:spf.flowmailer.net ip4:136.144.179.83 include:spf.crowdtech.com ip4:83.96.215.232 include:spf.protection.outlook.com include:_spf.paytsoftware.com include:spf.viper36" "5.nl include:amazonses.com include:spf.vanadium.mijnodoo.com ~all"	900

Checks

✓ TTLs within range #32

TTLs: A 15m, MX 5m, NS 6h. The NS TTL at the parent is 1h and in the zone 6h; resolvers may use either.
✓ No CNAME at the apex #33

The zone apex has no CNAME record.
i

Wildcard record

A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.

#34
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