SurfaceMap › l › loketgezondleven.nl

loketgezondleven.nl

Checked 2026-10-22 14:11 UTC · first added 2026-10-21

!Check could not complete

Domain & DNS

error

24 passed 2 warn 0 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration iDelegation iNameservers iSOA !DNSSEC !Records

Problems

!

NSEC3 with extra iterations or salt

DNSSEC · NSEC3 uses 10 iterations and a 13-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
!

Very low TTLs

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

#32

Recent checks

!

Full report

Domain & DNS report for loketgezondleven.nl ›

Mail

warn

25 passed 5 warn 0 failed

Areas

✓SPF !DMARC !DKIM ✓DNSSEC !MX !TLS iBIMI

Problems

!

Policy: quarantine

DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

#4
!

Hosts without IPv6

MX · The following MX hosts could not be resolved to IPv6 addresses: externemail.rivm.nl

#11
!

1024-bit DKIM key

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits). Rotate to a 2048-bit key.

#23
!

Addresses without reverse DNS

MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 2001:610:430:ffff::17:16 (externemail-mx2.rivm.nl). Ask your hosting provider to set one.

#30
!

Not configured

TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.

#32

Recent checks

!

Full report

Mail report for loketgezondleven.nl ›