SurfaceMap › c › chatbotgpt.fr

chatbotgpt.fr

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

Domain & DNS

fail

8 passed 3 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !DNSSEC

Problems

  • ✗
    No nameserver responds
    Nameservers · None of the nameserver addresses answered: ns5.alexhost.md (176.123.0.83): read udp 46.225.38.91:55406->176.123.0.83:53: i/o timeout; ns6.alexhost.md (176.123.0.84): read udp 46.225.38.91:55453->176.123.0.84:53: i/o timeout.
    #14
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 176.123.0.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    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 chatbotgpt.fr ›

Mail

fail

12 passed 5 warn 2 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
  • ✗
    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
  • !
    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: chatbotgpt.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
  • !
    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 chatbotgpt.fr ›