SurfaceMap › a › aquilenet.fr

aquilenet.fr

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

Domain & DNS

warn

24 passed 4 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns1.aquilenet.fr (glue 185.233.100.2, zone 185.233.100.2, 2a0c:e300::2); ns2.aquilenet.fr (glue 185.233.100.16, zone 185.233.100.16, 2a0c:e300::16). Update the glue at your registrar.
    #8
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.aquilenet.fr: "9.18.49-1~deb12u2-Debian"; ns2.aquilenet.fr: "9.20.29-1~deb13u1-Debian". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · retry 4h should be shorter than refresh 1h. Current values: refresh 1h, retry 4h, expire 28d, negative TTL 8h.
    #23
  • !
    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 aquilenet.fr ›

Mail

fail

21 passed 5 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
  • !
    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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: dkim (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 aquilenet.fr ›