SurfaceMap › m › myimagegpt.fr

myimagegpt.fr

Checked 2026-10-22 04:28 UTC · first added 2026-10-21
!Check could not complete

Domain & DNS

error

21 passed 3 warn 1 failed 1 errors

lookups failed for dnssec; results are incomplete

Areas

iRegistration !Delegation ✗Nameservers ✓SOA iDNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns6.alexhost.md (176.123.0.84): read udp 46.225.38.91:33214->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
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns5.alexhost.md: "9.11.36-RedHat-9.11.36-16.el8_10.16". Hide or replace the version string.
    #17

Recent checks

!

Full report

Domain & DNS report for myimagegpt.fr ›

Mail

fail

10 passed 4 warn 2 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
  • !
    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: myimagegpt.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
  • !
    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 myimagegpt.fr ›