SurfaceMap › r › resto.fr

resto.fr

Checked 2026-10-22 05:01 UTC · first added 2026-10-21
✗Problems found Score 46 of 100

Domain & DNS

warn

20 passed 5 warn 0 failed

Areas

iRegistration !Delegation !Nameservers ✓SOA !DNSSEC !Records

Problems

  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 212.3.255.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns.resto.be: "Microsoft DNS 6.1.7601 (1DB15F75)". Hide or replace the version string.
    #17
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 2h; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for resto.fr ›

Mail

fail

15 passed 3 warn 3 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 DKIM keys published
    DKIM · _domainkey.resto.fr does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • ✗
    Multiple SPF records
    SPF · Found 2 SPF records. Publishing more than one v=spf1 record causes a permerror; merge them into a single record.
    #16
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #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 resto.fr ›