SurfaceMap › l › ltonoord.nl

ltonoord.nl

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

Domain & DNS

error

22 passed 2 warn 2 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration !Delegation ✗Nameservers ✗SOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.duocast.net (2a01:1b0:4418::53): read tcp [2a01:4f8:1c1c:eebf::1]:60692->[2a01:1b0:4418::53]:53: read: connection reset by peer; ns1.quickhost.nl (2a01:1b0:4418::53): read tcp [2a01:4f8:1c1c:eebf::1]:60686->[2a01:1b0:4418::53]:53: read: connection reset by peer; ns2.duocast.net (2a01:1b1:4418::53): read tcp [2a01:4f8:1c1c:eebf::1]:38848->[2a01:1b1:4418::53]:53: read: connection reset by peer; ns2.quickhost.nl (2a01:1b1:4418::53): read tcp [2a01:4f8:1c1c:eebf::1]:38844->[2a01:1b1:4418::53]:53: read: connection reset by peer.
    #19
  • ✗
    Invalid contact address
    SOA · The SOA RNAME "hostmaster\\@duocast.net" contains an @; it must be written with a dot instead (hostmaster.example.com).
    #25
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.quickhost.nl, ns2.quickhost.nl; only in the zone: ns1.duocast.net, ns2.duocast.net. ns1.duocast.net, ns1.quickhost.nl, ns2.duocast.net, ns2.quickhost.nl report NS ns1.duocast.net ns2.duocast.net.
    #7
  • !
    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

Recent checks

!

Full report

Domain & DNS report for ltonoord.nl ›

Mail

fail

21 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    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
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    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 ltonoord.nl ›