SurfaceMap › r › refdoc.fr

refdoc.fr

Checked 2026-10-22 04:58 UTC · first added 2026-10-21
✗Problems found Score 46 of 100

Domain & DNS

warn

21 passed 4 warn 0 failed

Areas

iRegistration !Delegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: justin.nexylan.net. britney.nexylan.net, justin.nexylan.net, michael.nexylan.net report NS britney.nexylan.net justin.nexylan.net michael.nexylan.net.
    #7
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: britney.nexylan.net: "PowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)"; justin.nexylan.net: "PowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)"; michael.nexylan.net: "PowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)". 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 refdoc.fr ›

Mail

fail

22 passed 4 warn 3 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
  • ✗
    Multiple SPF records
    SPF · Found 4 SPF records. Publishing more than one v=spf1 record causes a permerror; merge them into a single record.
    #16
  • ✗
    TLSA records not DNSSEC-validated
    TLS · These MX hosts publish TLSA records that the resolver could not validate with DNSSEC, so senders ignore them or, if validation fails, may refuse delivery: mx1.nexylan.net, mx2.nexylan.net.
    #36
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (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
  • !
    Not configured
    TLS · MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35

Recent checks

✗

Full report

Mail report for refdoc.fr ›