invisalign.com

Checked 22 October 2026, 09:21 UTC · via 8.8.8.8
✗Problems found
24 passed 4 warnings 1 failed 3 info

SPF

fail

SPF record published

Found

Record
v=spf1 ip4:76.205.31.94 ip4:46.22.189.51 ip4:80.95.173.197 include:spf.protection.outlook.com ipv4:87.233.83.48 ipv6:2001:9a8:0:86:87:233:83:48 -all
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 1 of 10 DNS lookups #2
    SPF record needs 1 DNS lookups (limit is 10).
  • ✓ Ends with -all #3
    SPF record properly uses -all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✗
    Syntax errors
    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
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

warn

p=quarantine (_dmarc.invisalign.com)

Found

Record
v=DMARC1;p=quarantine;rua=mailto:UCC_Monitoring@aligntech.com
Found at
_dmarc.invisalign.com
External report address
mailto:UCC_Monitoring@aligntech.com (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:UCC_Monitoring@aligntech.comAggregate report addresses

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:UCC_Monitoring@aligntech.com
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

pass

Selectors: selector1, selector2, s1, s2

Found

Selectors
selector1, selector2, s1, s2
_domainkey
NXDOMAIN
SelectorKeyFlags
selector1RSA 2048 bits
selector2RSA 2048 bits
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: selector1, selector2, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, selector2, s1, s2
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: RSA 2048 bits; selector2: RSA 2048 bits; s1: RSA 2048 bits; s2: RSA 2048 bits.
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
0invisalign-com.mail.protection.outlook.comA 52.101.194.170 A 52.101.42.162 A 52.101.194.152 A 52.101.60.68 AAAA 2a01:111:f403:c946::1a AAAA 2a01:111:f403:f913::2 AAAA 2a01:111:f403:c946::6 AAAA 2a01:111:f403:c946::10mail-ch1pr02cu00102.inbound.protection.outlook.com ✓ mail-ea3pr05cu00102.inbound.protection.outlook.com ✓ mail-ch4pr04cu00300.inbound.protection.outlook.com ✓ mail-bnypr02cu00104.inbound.protection.outlook.com ✓ mail-ch0pr02cu00102.inbound.protection.outlook.com ✓ mail-cy4pr03cu00102.inbound.protection.outlook.com ✓ mail-ch5pr02cu00406.inbound.protection.outlook.com ✓ mail-ch4pr04cu00300.inbound.protection.outlook.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 1 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
invisalign-com.mail.protection.outlook.comnone-

Checks

  • !
    Not configured
    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
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38