SurfaceMap › v › vbet.fr

vbet.fr

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

Domain & DNS

warn

19 passed 3 warn 0 failed

Areas

iRegistration !Delegation iNameservers !SOA !DNSSEC iRecords

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.alphadnszone.com, ns2.alphadnszone.com, ns3.alphadnszone.com, ns4.alphadnszone.com, ns5.alphadnszone.com, ns6.alphadnszone.com; only in the zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net, ns1.alphadnszone.com, ns2.alphadnszone.com, ns3.alphadnszone.com, ns4.alphadnszone.com, ns5.alphadnszone.com, ns6.alphadnszone.com report NS dns1.p07.nsone.net dns2.p07.nsone.net dns3.p07.nsone.net dns4.p07.nsone.net.
    #7
  • !
    Unusual SOA timers
    SOA · refresh 7d is outside 20m–1d; expire 7d must be longer than refresh + retry; negative caching TTL (minimum) 1m40s is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 7d, retry 1m, expire 7d, negative TTL 1m40s.
    #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 vbet.fr ›

Mail

fail

22 passed 3 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
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    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
  • !
    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 vbet.fr ›