Identity
0
F
gov.uk
Posture Score: 52/100
Scanned May 8, 2026 at 8:19 AM UTC
Attack Surface
79
Reputation
77
Identity Findings
Critically weak DKIM key (~32 bits) for selector 'default'
RSA keys shorter than 1024 bits are trivially breakable. RFC 8301 requires minimum 1024 bits.
💡 Immediately generate a 2048-bit RSA key pair.
Critically weak DKIM key (~32 bits) for selector 'selector2'
RSA keys shorter than 1024 bits are trivially breakable. RFC 8301 requires minimum 1024 bits.
💡 Immediately generate a 2048-bit RSA key pair.
Critically weak DKIM key (~32 bits) for selector 'google'
RSA keys shorter than 1024 bits are trivially breakable. RFC 8301 requires minimum 1024 bits.
💡 Immediately generate a 2048-bit RSA key pair.
Critically weak DKIM key (~32 bits) for selector 'dkim'
RSA keys shorter than 1024 bits are trivially breakable. RFC 8301 requires minimum 1024 bits.
💡 Immediately generate a 2048-bit RSA key pair.
Critically weak DKIM key (~32 bits) for selector 'k1'
RSA keys shorter than 1024 bits are trivially breakable. RFC 8301 requires minimum 1024 bits.
💡 Immediately generate a 2048-bit RSA key pair.
Critically weak DKIM key (~32 bits) for selector 's2'
RSA keys shorter than 1024 bits are trivially breakable. RFC 8301 requires minimum 1024 bits.
💡 Immediately generate a 2048-bit RSA key pair.
Critically weak DKIM key (~32 bits) for selector 'mandrill'
RSA keys shorter than 1024 bits are trivially breakable. RFC 8301 requires minimum 1024 bits.
💡 Immediately generate a 2048-bit RSA key pair.
Critically weak DKIM key (~32 bits) for selector 'amazonses'
RSA keys shorter than 1024 bits are trivially breakable. RFC 8301 requires minimum 1024 bits.
💡 Immediately generate a 2048-bit RSA key pair.
No MX records found
The domain has no MX records and cannot receive email.
💡 Publish MX records pointing to your mail server(s).
Invalid DKIM syntax for selector 'default'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'selector1'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'selector2'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'google'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'dkim'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'mail'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'k1'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 's1'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 's2'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'mandrill'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'amazonses'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'cm'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'smtp'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
NS delegation mismatch
The registrar-delegated nameservers do not match the zone NS records.
💡 Update either the registrar NS delegation or the zone NS records to match.
Subdomain policy (sp=none) is weaker than domain policy (p=reject)
The subdomain policy is less restrictive than the organizational domain policy, leaving subdomains more vulnerable.
💡 Set sp=reject or remove sp= to inherit the domain policy.
No MTA-STS record found
Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.
💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.gov.uk/.well-known/mta-sts.txt
No CAA records found
No CAA records are configured. Any certificate authority can issue certificates for this domain.
💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"
No TLS-RPT record found
Without TLS-RPT, you will not receive reports about TLS negotiation failures.
💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@gov.uk").
ARC check skipped — no MX records
Cannot assess ARC support without MX records.
NS TTL mismatch between parent and authoritative zone
The NS record TTL in the parent zone (~7193s) differs significantly from the authoritative zone (~172800s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
DMARCbis np tag present: np=reject
The DMARC record includes the np (non-existent subdomain policy) tag, providing DMARCbis protection for non-existent subdomains.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
IPv6 readiness is good
IPv6 records are present and properly configured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
DKIM2 not detected
No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.
DMARC alignment: adkim=s, aspf=s
DKIM alignment is strict, SPF alignment is strict.
DMARC failure reporting: fo=1
Failure reports generated when any authentication mechanism fails.
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
DANE check skipped — no MX records
Cannot check DANE/TLSA without MX records.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open relay check skipped — no MX records
Cannot test for open relay without MX records.
SMTP compliance check skipped — no MX records
Cannot test SMTP compliance without MX records.
Port exposure check skipped — no MX records
Cannot scan ports without MX records.
STARTTLS downgrade check skipped — no MX records
Cannot test STARTTLS without MX records.
RFC 8058 one-click unsubscribe assessment
DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.
FCrDNS check skipped — no MX records
Cannot perform FCrDNS without MX records.
SOA record parameters
Serial: 1778227388, Refresh: 900s, Retry: 300s, Expire: 2419200s, Min TTL: 3600s
Attack Surface Findings
Weak DNSSEC RSA key: 336 bits
The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.
💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.
Weak DNSSEC RSA key: 336 bits
The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.
💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.
DNS ANY query returns 42 record(s)
The DNS server responds to ANY queries with 42 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
4 subdomain(s) discovered for gov.uk
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for gov.uk and its subdomains. Each certificate reveals subdomain names.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with 0 iteration(s) and salt '-'.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Listed on black.uribl.com
gov.uk is listed on blacklist black.uribl.com (response: 127.0.0.1).
💡 Visit the black.uribl.com website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Missing domain locks: clientTransferProhibited, clientDeleteProhibited
Domain gov.uk is missing protective locks: clientTransferProhibited, clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
HSTS enabled with preload on gov.uk
Strict-Transport-Security: max-age=31536000; preload
security.txt present
Found security.txt at https://gov.uk/.well-known/security.txt.
TLS certificate valid for 234 days
Certificate for gov.uk expires on 2026-12-28.
Certificate issued by GlobalSign RSA OV SSL CA 2018
The certificate for gov.uk is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for gov.uk uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for gov.uk uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for gov.uk contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on gov.uk.
No disposable email provider MX records
MX records for gov.uk do not match known disposable email provider patterns.
No wildcard MX records
No wildcard MX records detected for gov.uk.
Google Safe Browsing DNS check — no flag detected
DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.
No abuse contacts resolved
Could not resolve abuse contact information for MX IPs via abusix.org.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
Could not connect to webmail.gov.uk
HTTPS request to https://webmail.gov.uk failed or timed out.
WHOIS registration data
Registrar: No registrar listed. This domain is directly registered with Nominet. | Created: Unknown | Expires: Unknown | Updated: Unknown
WHOIS privacy protection not detected
Domain gov.uk does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
Could not determine domain age
WHOIS creation date could not be parsed for gov.uk.
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record found and configured
→
DMARC Policy
DMARC policy: reject
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature configured
→
DMARC Policy
DMARC policy: reject
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: reject
→
BIMI Record
Brand logo configured
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS failure reporting configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
Security Checks
MX Records
✗
SPF Record
✓
DKIM Record
✓
DMARC Policy
✓
BIMI Record
✓
CAA Records
✗
DNSSEC
✓
MTA-STS
✗
TLS-RPT
✓
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/gov.uk.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan gov.uk Again