SurfaceMap › i › invisalign.com

invisalign.com

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

Domain & DNS

warn

26 passed 2 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers ✓SOA !DNSSEC !Records

Problems

  • !
    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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change.
    #32

Recent checks

!

Full report

Domain & DNS report for invisalign.com ›

Mail

fail

24 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    Syntax errors
    SPF · Receivers reject the whole SPF record (permerror) because of: unknown mechanism "ipv4:87.233.83.48"; unknown mechanism "ipv6:2001:9a8:0:86:87:233:83:48".
    #25
  • !
    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
  • !
    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 invisalign.com ›