What QuantGuard™ looks at
- Spoofing protection
- Whether your DMARC policy tells receivers to reject forged mail.
- Encrypted delivery
- Whether an MTA-STS policy stops mail being sent unencrypted.
- Delivery reports
- Whether TLS reporting tells you when encrypted delivery fails.
- Mail provider
- Who handles your mail, and their post-quantum plans.
What a QuantGuard™ report shows
Taken from our own report on quantguard.co.uk.
DMARC policy doesn't enforce (p=none) quantguard.co.uk Low hygiene
- dmarc
- v=DMARC1; p=none;
Spoofed mail is reported but still delivered.
How to fix: Publish a DMARC record (`_dmarc` TXT) and move to `p=quarantine` or `p=reject` once reports show legitimate mail is aligned.
No MTA-STS policy quantguard.co.uk Low hygiene
Mail sent to this domain can be downgraded to an unencrypted connection by an attacker on the network path.
How to fix: Publish MTA-STS (a `_mta-sts` TXT record and a policy at `https://mta-sts.<domain>/.well-known/mta-sts.txt`) so sending servers require TLS.
Mail is handled by Namecheap hosting quantguard.co.uk Info hygiene
- mx
- mx1-hosting.jellyfish.systems, mx2-hosting.jellyfish.systems, mx3-hosting.jellyfish.systems
Identified from the domain's MX records.
How to fix: No action required.
No TLS-RPT record quantguard.co.uk Info hygiene
You won't hear about senders failing to connect securely.
How to fix: Publish a TLS-RPT record (`_smtp._tls` TXT, `v=TLSRPTv1; rua=mailto:...`) to receive TLS failure reports.
Need more than a public scan?
The free scan sees what the internet sees. A QuantGuard™ assessment covers what it cannot: internal systems, keys and suppliers.
Every QuantGuard™ engagement is delivered by Dirhami Investment Technology Ltd.