SurfaceMap › b › bpifrance-creation.fr

bpifrance-creation.fr

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

Domain & DNS

fail

18 passed 3 warn 5 failed

Areas

iRegistration !Delegation ✗Nameservers ✗SOA !DNSSEC ✗Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: dns2.ddn.fr (51.38.51.153): read udp 46.225.38.91:49978->51.38.51.153:53: read: connection refused.
    #14
  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns-1266.awsdns-30.org (205.251.196.242): REFUSED, authoritative=false; ns-1266.awsdns-30.org (2600:9000:5304:f200::1): REFUSED, authoritative=false; ns-1922.awsdns-48.co.uk (205.251.199.130): REFUSED, authoritative=false; ns-1922.awsdns-48.co.uk (2600:9000:5307:8200::1): REFUSED, authoritative=false; ns-409.awsdns-51.com (205.251.193.153): REFUSED, authoritative=false; ns-409.awsdns-51.com (2600:9000:5301:9900::1): REFUSED, authoritative=false; ns-800.awsdns-36.net (205.251.195.32): REFUSED, authoritative=false; ns-800.awsdns-36.net (2600:9000:5303:2000::1): REFUSED, authoritative=false.
    #15
  • ✗
    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: ns-1266.awsdns-30.org (205.251.196.242): ; ns-1266.awsdns-30.org (2600:9000:5304:f200::1): ; ns-1922.awsdns-48.co.uk (205.251.199.130): ; ns-1922.awsdns-48.co.uk (2600:9000:5307:8200::1): ; ns-409.awsdns-51.com (205.251.193.153): ; ns-409.awsdns-51.com (2600:9000:5301:9900::1): ; ns-800.awsdns-36.net (205.251.195.32): ; ns-800.awsdns-36.net (2600:9000:5303:2000::1): .
    #19
  • ✗
    Invalid contact address
    SOA · The SOA RNAME "tech\\@dns1.ddn.fr" contains an @; it must be written with a dot instead (hostmaster.example.com).
    #25
  • ✗
    CNAME at the apex
    Records · The zone apex is a CNAME to d3phl773vony6a.cloudfront.net. A CNAME can't coexist with the SOA and NS records (RFC 1034); use your provider's ALIAS/flattening feature instead.
    #33
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: dns1.ddn.fr, dns2.ddn.fr, dns3.ddn.fr; only in the zone: ns-1266.awsdns-30.org, ns-1922.awsdns-48.co.uk, ns-409.awsdns-51.com, ns-800.awsdns-36.net.
    #7
  • !
    No EDNS
    Nameservers · These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns-1266.awsdns-30.org (205.251.196.242), ns-1266.awsdns-30.org (2600:9000:5304:f200::1), ns-1922.awsdns-48.co.uk (205.251.199.130), ns-1922.awsdns-48.co.uk (2600:9000:5307:8200::1), ns-409.awsdns-51.com (205.251.193.153), ns-409.awsdns-51.com (2600:9000:5301:9900::1), ns-800.awsdns-36.net (205.251.195.32), ns-800.awsdns-36.net (2600:9000:5303:2000::1).
    #20
  • !
    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 bpifrance-creation.fr ›

Mail

fail

2 passed 3 warn 3 failed

Areas

✗SPF ✗DMARC ✗DKIM !DNSSEC !MX 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 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.bpifrance-creation.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
  • !
    No MX records
    MX · No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").
    #9
  • !
    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

Recent checks

✗

Full report

Mail report for bpifrance-creation.fr ›