SurfaceMap › s › sara.be

sara.be

Checked 2026-10-22 07:10 UTC · first added 2026-10-21
✗Problems found Score 39 of 100

Domain & DNS

fail

23 passed 3 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: dns1.stabletransit.com (69.20.95.4): REFUSED, authoritative=false; dns2.stabletransit.com (65.61.188.4): REFUSED, authoritative=false; ns1.stabletransit.com (69.20.95.4): REFUSED, authoritative=false; ns2.stabletransit.com (65.61.188.4): REFUSED, authoritative=false.
    #15
  • ✗
    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: dns1.stabletransit.com (69.20.95.4): ; dns2.stabletransit.com (65.61.188.4): ; ns1.stabletransit.com (69.20.95.4): ; ns2.stabletransit.com (65.61.188.4): .
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: dns1.stabletransit.com, dns2.stabletransit.com, ns1.stabletransit.com, ns2.stabletransit.com. ns1.openprovider.nl, ns2.openprovider.be, ns3.openprovider.eu report NS ns1.openprovider.nl ns2.openprovider.be ns3.openprovider.eu.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.openprovider.nl: "2026.10.8"; ns2.openprovider.be: "2026.10.8"; ns3.openprovider.eu: "2026.10.8". Hide or replace the version string.
    #17
  • !
    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 sara.be ›

Mail

fail

9 passed 4 warn 2 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
  • ✗
    No SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • !
    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: mail.op-email.eu
    #11
  • !
    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 sara.be ›