tcs.com

Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

DNSSEC · The earliest signature expires at 2026-10-23 23:48 UTC (in 37h0m0s). Check that automatic re-signing works.

DNSSEC · NSEC3 uses 50 iterations and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.

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

MX · The following MX hosts could not be resolved to IPv6 addresses: Inblrg04.tcs.com, Inblrg05.tcs.com, Inmumg04.tcs.com, Inmumg05.tcs.com, inblrg01.tcs.com, inblrg03.tcs.com, inchng01.tcs.com, inchng02.tcs.com, inchng04.tcs.com, inchng05.tcs.com, inmumg01.tcs.com, inmumg02.tcs.com, uklong01.tcs.com, usnjyg01.tcs.com

MX · Found 14 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.

DNSSEC · DNSKEY signatures expire at 2026-10-23T23:48:16Z (in 37h0m0s). Check that re-signing works.

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: s2 (1024 bits). Rotate to a 2048-bit key.

MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 45.249.218.97 (Inmumg04.tcs.com), 45.249.218.122 (Inmumg05.tcs.com). Ask your hosting provider to set one.

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.

TLS · MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".