SurfaceMap › w › webhostingtalk.nl

webhostingtalk.nl

Checked 2026-10-22 17:11 UTC · first added 2026-10-21
!Check could not complete

Domain & DNS

error

25 passed 2 warn 0 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration ✓Delegation iNameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Signed but not delegated securely
    DNSSEC · 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
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 10 iterations 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

Recent checks

!

Full report

Domain & DNS report for webhostingtalk.nl ›

Mail

fail

17 passed 6 warn 1 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • !
    5 of 10 DNS lookups, with problems
    SPF · SPF record needs 5 DNS lookups (limit is 10). Problems found: include:_spf.moneybird.nl does not exist or has no records; include:mailing.webhostingtalk.nl does not exist or has no records.
    #2
  • !
    Signed, but no DS at parent
    DNSSEC · The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.
    #8
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    2 void lookups
    SPF · 2 include/redirect targets does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 2001:550:2:61::2fc:100 (lastmx.spamexperts.net). 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 webhostingtalk.nl ›