SurfaceMap › g › geo.fr

geo.fr

Checked 2026-10-22 03:13 UTC · first added 2026-10-21
✗Problems found Score 62 of 100

Domain & DNS

fail

22 passed 2 warn 1 failed

Areas

iRegistration ✗Delegation ✓Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Nameserver names don't resolve
    Delegation · These nameservers have no A or AAAA record, so they can't be reached (lame delegation): venus.vp-dns.net.
    #9
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: venus.vp-dns.net. deimos.vp-dns.net, phobos.vp-dns.net report NS deimos.vp-dns.net phobos.vp-dns.net.
    #7
  • !
    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

Recent checks

✗

Full report

Domain & DNS report for geo.fr ›

Mail

fail

22 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
  • !
    Uses deprecated ptr mechanism
    SPF · The ptr mechanism in SPF records is deprecated due to performance issues and should be avoided.
    #1
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    More than 5 MX records
    MX · Found 6 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • !
    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 geo.fr ›