SurfaceMap › r › recht.nl

recht.nl

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

Domain & DNS

error

25 passed 1 warn 2 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration iDelegation ✗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.argewebhosting.eu (31.25.98.210): read tcp 46.225.38.91:48766->31.25.98.210:53: i/o timeout; ns1.argewebhosting.eu (2a05:1500:702:0:1c00:eff:fe00:ce): read tcp [2a01:4f8:1c1c:eebf::1]:51964->[2a05:1500:702:0:1c00:eff:fe00:ce]:53: i/o timeout.
    #19
  • ✗
    Invalid contact address
    SOA · The SOA RNAME "hostmaster\\@argeweb.nl" contains an @; it must be written with a dot instead (hostmaster.example.com).
    #25
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 1 iteration and a 1-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 recht.nl ›

Mail

fail

17 passed 4 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
  • !
    Ends with ?all (neutral)
    SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.
    #3
  • !
    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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: in1-smtp.messagingengine.com, in2-smtp.messagingengine.com
    #11
  • !
    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 recht.nl ›