shiksha.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-14.akam.net: "41824.4"; a1-14.akam.net: "41824.9"; a12-65.akam.net: "48878.33"; a12-65.akam.net: "48878.32"; a13-66.akam.net: "41824.7"; a13-66.akam.net: "41824.9"; a16-67.akam.net: "48878.33"; a16-67.akam.net: "48878.26"; a24-64.akam.net: "48878.26"; a3-65.akam.net: "41824.6"; a3-65.akam.net: "41824.11". Hide or replace the version string.

SOA · negative caching TTL (minimum) 2m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 2h, retry 5m, expire 7d, negative TTL 2m.

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.

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

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: shiksha-com.mail.protection.outlook.com

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

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.