sho.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns0004.secondary.cloudflare.com: "2026.10.2"; ns0243.secondary.cloudflare.com: "2026.10.2". 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.

SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.

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: mxa-00262c01.gslb.pphosted.com, mxb-00262c01.gslb.pphosted.com

DMARC · DMARC policy only applies to 10% of failing mail (pct=10). Raise pct to 100 once you are confident in your setup.

DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

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.