princess.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: asia2.akam.net: "48878.30"; eur6.akam.net: "41824.8"; ns1-136.akam.net: "41824.9"; ns1-136.akam.net: "41824.5"; ns1-208.akam.net: "41824.7"; ns1-208.akam.net: "41824.11"; usc4.akam.net: "48878.31"; use9.akam.net: "48878.26"; usw1.akam.net: "41824.10"; usw4.akam.net: "48878.33"; usw4.akam.net: "48878.31". Hide or replace the version string.

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.

Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 2h; resolvers may use either.

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

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: mail3.princess.com, mail4.princess.com

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

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.