tixr.com

Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ns-1704.awsdns-21.co.uk. ns-109.awsdns-13.com, ns-1399.awsdns-46.org, ns-1704.awsdns-21.co.uk, ns-920.awsdns-51.net report NS ns-109.awsdns-13.com ns-1399.awsdns-46.org ns-1704.awsdns-21.co.uk ns-920.awsdns-51.net.

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 (1m). 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.

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

DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

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

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.