sunglasshut.com

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

SPF

warn

SPF record published

Found

Record
v=spf1 ip4:52.29.114.6 ip4:18.194.24.66 ip4:35.159.3.28 ip4:46.226.52.101 ip4:85.158.142.101 ip4:85.158.142.203 ip4:85.158.142.107 ip4:85.158.142.103 ip4:46.226.52.197 ip4:46.226.52.203 ip4:46.226.52.199 ip4:85.158.142.200 ip4:46.226.52.107 ip4:46.226.52.103 ip4:85.158.142.193 ip4:200.186.189.26/28 ip4:200.186.231.230/28 ip4:200.186.189.26 ip4:200.186.189.26 ip4:85.158.136.0/21 ip4:193.109.254.0/23 ip4:194.106.220.0/23 ip4:195.245.230.0/23 ip4:95.131.104.0/21 ip4:46.226.48.0/21 ip4:216.82.240.0/20 ip4:67.219.240.0/20 ip4:117.120.16.0/21 ip4:103.9.96.0/22 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/14 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/48 ip4:51.4.72.0/24 ip4:51.5.72.0/24 ip4:51.5.80.0/27 ip4:51.4.80.0/27 ip6:2a01:4180:4051:0800::/64 ip6:2a01:4180:4050:0800::/64 ip6:2a01:4180:4051:0400::/64 ip6:2a01:4180:4050:0400::/64 ip4:52.211.17.155 ip4:52.51.15.72 ip4:52.30.186.166 ip4:52.33.64.93 ip4:52.27.180.120 ip4:52.41.248.36 ip4:168.87.137.54 ip4:168.87.137.55 -all
DNS lookups
0 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 0 of 10 DNS lookups #2
    SPF record needs 0 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.
  • !
    Broad IP ranges
    These ranges authorize tens of thousands of addresses or more: ip4:40.92.0.0/15, ip4:52.100.0.0/14. Check that you really own and send from all of them.
    #27

DMARC

pass

p=reject (_dmarc.sunglasshut.com)

Found

Record
v=DMARC1; p=reject; rua=mailto:DMARCReport@luxottica.com,mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:DMARCReport@luxottica.com,mailto:dmarc_ruf@emaildefense.proofpoint.com; fo=1;
Found at
_dmarc.sunglasshut.com
External report address
mailto:DMARCReport@luxottica.com (authorized)
External report address
mailto:dmarc_rua@emaildefense.proofpoint.com (authorized)
External report address
mailto:dmarc_ruf@emaildefense.proofpoint.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:DMARCReport@luxottica.com,mailto:dmarc_rua@emaildefense.proofpoint.comAggregate report addresses
rufmailto:DMARCReport@luxottica.com,mailto:dmarc_ruf@emaildefense.proofpoint.comFailure report addresses
fo1Failure reporting options

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:DMARCReport@luxottica.com, mailto:dmarc_rua@emaildefense.proofpoint.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

pass

Selectors: selector1

Found

Selectors
selector1
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits

Checks

  • ✓ Keys found: selector1 #7
    DKIM keys found for this domain with selectors: selector1
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: 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
0sunglasshut-com.mail.protection.outlook.comA 52.101.73.126 A 52.101.185.24 A 52.101.209.28 A 52.101.181.156mail-am8pr83cu00106.inbound.protection.outlook.com ✓ mail-zrxpr07cu00100.inbound.protection.outlook.com ✓ mail-cpjpr05cu00104.inbound.protection.outlook.com ✓ mail-wa4pr05cu00104.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.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: sunglasshut-com.mail.protection.outlook.com
    #11
  • !
    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 4 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
sunglasshut-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