SurfaceMap › u › u-bordeaux2.fr

u-bordeaux2.fr

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

Domain & DNS

fail

21 passed 3 warn 1 failed

Areas

iRegistration ✗Delegation iNameservers !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): tibere.u-bordeaux2.fr.
    #9
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: tibere.u-bordeaux2.fr. camus.dr15.cnrs.fr, hippocrate.u-bordeaux2.fr report NS camus.dr15.cnrs.fr hippocrate.u-bordeaux2.fr.
    #7
  • !
    Unusual SOA timers
    SOA · refresh 36h is outside 20m–1d. Current values: refresh 36h, retry 15m, expire 21d, negative TTL 3h.
    #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 u-bordeaux2.fr ›

Mail

fail

8 passed 3 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.u-bordeaux2.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: mta-in01.u-bordeaux.fr, mta-in02.u-bordeaux.fr, mta-in03.u-bordeaux.fr, mta-in04.u-bordeaux.fr
    #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 u-bordeaux2.fr ›