SurfaceMap › c › crdp-strasbourg.fr

crdp-strasbourg.fr

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

Domain & DNS

fail

19 passed 3 warn 3 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns1.u-strasbg.fr (130.79.200.1): REFUSED, authoritative=false; ns1.u-strasbg.fr (2001:660:2402::1): REFUSED, authoritative=false.
    #15
  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns2.ac-strasbourg.fr (2001:660:470f::2): 38 records. Restrict zone transfers to your secondary servers.
    #18
  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.u-strasbg.fr (130.79.200.1): ; ns1.u-strasbg.fr (2001:660:2402::1): .
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ns2.ac-strasbourg.fr. ns1.crdp-strasbourg.fr, ns2.ac-strasbourg.fr report NS ns1.crdp-strasbourg.fr ns1.u-strasbg.fr ns2.ac-strasbourg.fr.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.u-strasbg.fr: "9.20.24-1ubuntu0.4-Ubuntu". 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 crdp-strasbourg.fr ›

Mail

fail

5 passed 6 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 SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • ✗
    No DKIM keys published
    DKIM · _domainkey.crdp-strasbourg.fr does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #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: mail.crdp-strasbourg.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
  • !
    Hosts are CNAMEs
    MX · MX records must point to a host name with A/AAAA records, not to a CNAME: mail.crdp-strasbourg.fr -> all.crdp-strasbourg.fr
    #22
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 194.254.145.8 (mail.crdp-strasbourg.fr). Ask your hosting provider to set one.
    #30
  • !
    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 crdp-strasbourg.fr ›