sunglasshut.com

Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: a1-51.akam.net, a10-66.akam.net, a2-67.akam.net, a3-65.akam.net, a7-66.akam.net; only in the zone: a1-83.akam.net, a13-66.akam.net, a20-67.akam.net, a28-65.akam.net, a9-66.akam.net. a1-51.akam.net, a1-83.akam.net, a10-66.akam.net, a13-66.akam.net, a2-67.akam.net, a20-67.akam.net, a22-64.akam.net, a28-65.akam.net, a3-65.akam.net, a7-66.akam.net, a9-66.akam.net report NS a1-83.akam.net a13-66.akam.net a20-67.akam.net a22-64.akam.net a28-65.akam.net a9-66.akam.net.

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-51.akam.net: "41824.5"; a1-51.akam.net: "41824.4"; a1-83.akam.net: "41824.9"; a1-83.akam.net: "41824.6"; a10-66.akam.net: "48878.27"; a10-66.akam.net: "48878.31"; a13-66.akam.net: "41824.10"; a2-67.akam.net: "48878.30"; a2-67.akam.net: "48878.26"; a20-67.akam.net: "48878.30"; a20-67.akam.net: "48878.32"; a22-64.akam.net: "48878.33"; a22-64.akam.net: "48878.30"; a28-65.akam.net: "48878.26"; a28-65.akam.net: "48878.29"; a3-65.akam.net: "41824.6"; a3-65.akam.net: "41824.11"; a7-66.akam.net: "41824.9"; a7-66.akam.net: "41824.6"; a9-66.akam.net: "41824.9"; a9-66.akam.net: "41824.8". Hide or replace the version string.

SOA · retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 14d, negative TTL 1h.

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.

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

MX · The following MX hosts could not be resolved to IPv6 addresses: sunglasshut-com.mail.protection.outlook.com

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

SPF · 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.

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.