princess.com

Checked 22 October 2026, 10:21 UTC · via 8.8.8.8
!Passed with warnings
22 passed 5 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx include:spf.protection.outlook.com include:spf.sabre.com -all
DNS lookups
4 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 4 of 10 DNS lookups #2
    SPF record needs 4 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.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ 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=reject (_dmarc.princess.com)

Found

Record
v=DMARC1; p=reject; rua=mailto:carnivaldmarc@carnival.com; pct=100
Found at
_dmarc.princess.com
External report address
mailto:carnivaldmarc@carnival.com (not authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
pct100Percentage of mail the policy applies to
ruamailto:carnivaldmarc@carnival.comAggregate report addresses

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ 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:carnivaldmarc@carnival.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:carnivaldmarc@carnival.com (needs princess.com._report._dmarc.carnival.com). Ask the report provider to publish the record, or check the address.
    #29

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7

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

3 mail servers

Found

PriorityHostRecordsReverse DNS
10carnival-com.mail.protection.outlook.comA 52.101.42.64 A 52.101.60.154 A 52.101.8.68 A 52.101.9.11 AAAA 2a01:111:f403:c936:: AAAA 2a01:111:f403:c95d:: AAAA 2a01:111:f403:c902::2 AAAA 2a01:111:f403:c903::3mail-mw2pr05cu00100.inbound.protection.outlook.com ✓ mail-bn0pr03cu00302.inbound.protection.outlook.com ✓ mail-dm5pr05cu00104.inbound.protection.outlook.com ✓ mail-bl1pr02cu00103.inbound.protection.outlook.com ✓ mail-cy7pr05cu00100.inbound.protection.outlook.com ✓ mail-ph8pr05cu00300.inbound.protection.outlook.com ✓ mail-sj0pr03cu01602.inbound.protection.outlook.com ✓ mail-mw2pr02cu00503.inbound.protection.outlook.com ✓
20mail3.princess.comA 151.124.32.87mail3.princess.com ✓
20mail4.princess.comA 151.124.32.86mail4.princess.com ✓

Checks

  • ✓ 3 MX records #9
    Found 3 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mail3.princess.com, mail4.princess.com
    #11
  • ✓ Redundant MX hosts #12
    Found 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 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 10 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
carnival-com.mail.protection.outlook.comnone-
mail3.princess.comnone-
mail4.princess.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