base.org
Needs work, with 1 thing to fix
base.org scored 80/100 (grade C). The main issue is more than one SPF record. Detected senders: Google Workspace.
Checked 2026-10-04 02:05 UTC · fresh check
Merge the SPF records into one
base.org must publish exactly one SPF record. Delete all existing v=spf1 records and publish this one, which keeps every active mechanism they listed.
base.org
Some DNS providers want “@” here instead of the full domain.
v=spf1 include:_spf.google.com include:amazonses.com -all
v=spf1 include:_spf.google.com -all v=spf1 include:amazonses.com -all
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?More than one SPF recordFailing
- Fail: More than one SPF record
base.org publishes 2 SPF records. RFC 7208 treats that as a permanent error, so SPF fails for every message. Merge them into a single record.
How to fix this
DKIMAre your emails signed?DKIM key publishedPass
- Pass: DKIM key published
base.org publishes a DKIM key under google.
DMARCWhat happens to fakes?No issues foundPass
Nothing to report.
AlignmentDoes it match your From?SPF alignment is unknownInfo
- Info: SPF alignment is unknown
The SPF record of base.org is invalid (spf.multiple), so receivers return a permanent error for every message and SPF cannot authenticate any sender for DMARC. DMARC depends on DKIM until the record is fixed.
BIMICan inboxes show your logo?No BIMI recordInfo
- Info: No BIMI record
No BIMI record at default._bimi.base.org. BIMI is optional: it shows your logo next to your mail in supporting inboxes once DMARC is enforced.
How to fix this
MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
- Info: No MTA-STS record
No MTA-STS record at _mta-sts.base.org. 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.base.org. 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 base.org publishes an MTA-STS policy at https://mta-sts.base.org/.well-known/mta-sts.txt. Change the id whenever the policy file changes.
_mta-sts.base.org
Some DNS providers want just “_mta-sts” here.
v=STSv1; id=202610040205
Host the MTA-STS policy filepolicy-file
Serve this file over HTTPS with a valid certificate for mta-sts.base.org. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.
https://mta-sts.base.org/.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: alt3.aspmx.l.google.com mx: alt4.aspmx.l.google.com mx: inbound-smtp.us-east-1.amazonaws.com max_age: 604800
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to base.org, 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.base.org
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@base.org, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.base.org with the value v=TLSRPTv1; rua=mailto:<that address>.
Prepare BIMIinstruction
BIMI shows your logo next to messages in supporting inboxes, but only for mail that passes DMARC under an enforced policy.
Applies to: default._bimi.base.org
- Enforce DMARC first: p=quarantine or p=reject at 100% (no pct below 100). 2. Convert your logo to an SVG Tiny PS file and host it over HTTPS, for example https://base.org/bimi/logo.svg. 3. For Gmail and Apple Mail, obtain a VMC or CMC certificate for the logo. 4. Publish a TXT record at default._bimi.base.org with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.