tcm.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-17.akam.net: "41824.10"; a1-17.akam.net: "41824.9"; a12-64.akam.net: "48878.29"; a12-64.akam.net: "48878.30"; a16-65.akam.net: "48878.29"; a3-66.akam.net: "41824.9"; a3-66.akam.net: "41824.7"; a6-67.akam.net: "48878.29"; a6-67.akam.net: "48878.27"; a9-64.akam.net: "41824.6"; a9-64.akam.net: "41824.7". 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), AAAA (20s). Low TTLs are useful just before a planned change.

DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

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 IP addresses: mxa-00241e02.gslb.pphosted.com, mxb-00241e02.gslb.pphosted.com

MX · The following MX hosts could not be resolved to IPv6 addresses: mxa-00241e02.gslb.pphosted.com, mxb-00241e02.gslb.pphosted.com

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.