SurfaceMap › a › archimed.fr

archimed.fr

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

Domain & DNS

fail

18 passed 3 warn 3 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): srv-dns-01.
    #9
  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: dns-02.archimed.fr (83.145.86.7): read udp 46.225.38.91:43762->83.145.86.7:53: i/o timeout.
    #14
  • ✗
    Open recursion
    Nameservers · These nameservers resolve names for anyone, which makes them usable for DNS amplification attacks and cache poisoning: dns-01.archimed.fr (83.145.86.8). Disable recursion on authoritative servers.
    #16
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: srv-dns-01. dns-01.archimed.fr report NS dns-01.archimed.fr dns-02.archimed.fr srv-dns-01.
    #7
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 83.145.86.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    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 archimed.fr ›

Mail

fail

20 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
  • !
    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: vade-mx-fr01.hornetsecurity.com, vade-mx-fr02.hornetsecurity.com, vade-mx-eu-fallback01.hornetsecurity.com, vade-mx-eu-fallback02.hornetsecurity.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 archimed.fr ›