SurfaceMap › w › whmcs.com

whmcs.com

Checked 2026-10-22 11:31 UTC · first added 2026-10-21
✗Problems found Score 66 of 100

Domain & DNS

warn

23 passed 3 warn 0 failed

Areas

iRegistration !Delegation !Nameservers ✓SOA !DNSSEC ✓Records

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns1.whmcs.com (glue 162.159.8.226, zone 162.159.8.226, 2400:cb00:2049:1::a29f:8e2); ns2.whmcs.com (glue 162.159.9.128, zone 162.159.9.128, 2400:cb00:2049:1::a29f:980). Update the glue at your registrar.
    #8
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.whmcs.com: "2026.10.2"; ns2.whmcs.com: "2026.10.2". 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 whmcs.com ›

Mail

fail

25 passed 5 warn 1 failed

Areas

✓SPF !DMARC ✓DKIM !DNSSEC !MX !TLS ✗BIMI

Problems

  • ✗
    DMARC not strict enough for BIMI
    BIMI · Mail clients will not show the logo. BIMI requires a subdomain policy other than sp=none.
    #39
  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Subdomains unprotected (sp=none)
    DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    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 whmcs.com ›