SurfaceMap › e › ehne.fr

ehne.fr

Checked 2026-10-22 02:42 UTC · first added 2026-10-21
✗Problems found Score 37 of 100

Domain & DNS

fail

21 passed 4 warn 2 failed

Areas

✗Registration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Expires in 2 days
    Registration · The registration expires on 2026-10-24. Renew it now or enable auto-renewal.
    #3
  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns0.paris-sorbonne.fr (195.220.216.41): read udp 46.225.38.91:57846->195.220.216.41:53: i/o timeout; ns0.sorbonne-universite.fr (134.157.23.111): read udp 46.225.38.91:46266->134.157.23.111:53: i/o timeout; ns2.paris-sorbonne.fr (195.220.216.27): read udp 46.225.38.91:53678->195.220.216.27:53: read: no route to host; ns3.paris-sorbonne.fr (195.220.209.19): read udp 46.225.38.91:35130->195.220.209.19:53: i/o timeout.
    #14
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns3.paris-sorbonne.fr; only in the zone: ns0.paris-sorbonne.fr, ns0.sorbonne-universite.fr, ns1.sorbonne-universite.fr. ns1.paris-sorbonne.fr, ns1.sorbonne-universite.fr report NS ns0.paris-sorbonne.fr ns0.sorbonne-universite.fr ns1.paris-sorbonne.fr ns1.sorbonne-universite.fr ns2.paris-sorbonne.fr.
    #7
  • !
    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: ns1.paris-sorbonne.fr: "9.16.48-Debian". 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

Recent checks

✗

Full report

Domain & DNS report for ehne.fr ›

Mail

fail

16 passed 7 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
  • !
    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
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: muscovite.paris-sorbonne.fr
    #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
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    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 ehne.fr ›