ui.com
Good, with 2 things to fix
ui.com scored 84/100 (grade B). The main issues are DKIM key shorter than 2048 bits and DMARC: subdomain policy is weaker than the domain policy. Detected senders: Google Workspace, Amazon SES and Zendesk.
Checked 2026-10-04 02:03 UTC · fresh check
Strengthen the DMARC policy
Rejects mail that fails DMARC, the strongest protection against spoofing. Changes: Subdomains move one step, from sp=quarantine to the domain policy (p=reject).
_dmarc.ui.com
Some DNS providers want just “_dmarc” here.
v=DMARC1; p=reject; rua=mailto:dmarc-reports@ui.com; adkim=s; aspf=r
v=DMARC1; p=reject; aspf=r; adkim=s; sp=quarantine; rua=mailto:dmarc-reports@ui.com
How to apply it
- Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
- Find the existing TXT record with that name and replace its value.
- Save, then come back and re-check. DNS changes can take up to a few hours to show.
All checks
MXCan servers find your inbox?No issues foundPass
Nothing to report.
SPFWho may send as you?No issues foundPass
Nothing to report.
DKIMAre your emails signed?DKIM key shorter than 2048 bitsNeeds attention
- Warning: DKIM key shorter than 2048 bits
google (1024-bit) uses an RSA key below 2048 bits. Short keys can be factored and some receivers treat them as weak. Rotate to a 2048-bit key at your sending provider.
- Pass: DKIM key published
ui.com publishes a DKIM key under google, k2, k3.
DMARCWhat happens to fakes?Subdomain policy is weaker than the domain policyNeeds attention
- Warning: Subdomain policy is weaker than the domain policy
sp=quarantine is weaker than p=reject, so attackers can spoof any subdomain of ui.com (for example billing.ui.com) even though the main domain is protected.
How to fix this - Info: DMARC uses strict alignment
With adkim=s or aspf=s the DKIM d= domain or the bounce domain must equal the From domain exactly; a subdomain is not enough. Third-party senders that sign or bounce from a subdomain (or their own domain) will then fail DMARC unless they are configured to use your exact domain.
AlignmentDoes it match your From?No issues foundPass
Nothing to report.
BIMICan inboxes show your logo?No issues foundPass
Nothing to report.
MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
- Info: No MTA-STS record
No MTA-STS record at _mta-sts.ui.com. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.
How to fix this
TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
- Info: No TLS-RPT record
No TLS reporting record at _smtp._tls.ui.com. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this
Other fixes
Publish the MTA-STS recordTXT
Tells sending servers that ui.com publishes an MTA-STS policy at https://mta-sts.ui.com/.well-known/mta-sts.txt. Change the id whenever the policy file changes.
_mta-sts.ui.com
Some DNS providers want just “_mta-sts” here.
v=STSv1; id=202610040203
Host the MTA-STS policy filepolicy-file
Serve this file over HTTPS with a valid certificate for mta-sts.ui.com. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.
https://mta-sts.ui.com/.well-known/mta-sts.txt
version: STSv1 mode: testing mx: aspmx.l.google.com mx: alt1.aspmx.l.google.com mx: alt2.aspmx.l.google.com mx: aspmx2.googlemail.com mx: aspmx3.googlemail.com max_age: 604800
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to ui.com, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.
Applies to: _smtp._tls.ui.com
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@ui.com, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.ui.com with the value v=TLSRPTv1; rua=mailto:<that address>.