grab.co

grab.co · Last checked 2026-10-04 02:17 UTC

grab.co

Needs work, with 1 thing to fix

grab.co scored 70/100 (grade C). The main issue is no SPF record. Detected senders: Google Workspace.

Checked 2026-10-04 02:17 UTC · fresh check

3 passed1 failing4 for informationDetected senders: Google Workspace
Fix this firstThe change with the biggest effect

Publish an SPF record

Lists the sending services detected for grab.co (Google Workspace) and rejects everything else. Add any other service that sends as grab.co before publishing. Changes: Added include:_spf.google.com for Google Workspace.

TypeTXT
Name / Host
grab.co

Some DNS providers want “@” here instead of the full domain.

Value
v=spf1 include:_spf.google.com -all

How to apply it

  1. Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
  2. Add a new TXT record with the name and value above.
  3. 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 SPF recordFailing
  • Fail: No SPF record

    grab.co publishes no TXT record starting with "v=spf1", so receivers cannot tell which servers may send mail for it. Publish one SPF record listing every service that sends as grab.co.

    How to fix this
DKIMAre your emails signed?DKIM key publishedPass
  • Pass: DKIM key published

    grab.co publishes a DKIM key under google.

DMARCWhat happens to fakes?DMARC policy is quarantine; consider rejectInfo
  • Info: DMARC policy is quarantine; consider reject

    Failing mail goes to spam rather than being refused. When reports show no legitimate failures, reject gives the strongest protection.

    How to fix this
AlignmentDoes it match your From?No issues foundPass

Nothing to report.

BIMICan inboxes show your logo?No BIMI recordInfo
  • Info: No BIMI record

    No BIMI record at default._bimi.grab.co. 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.grab.co. 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.grab.co. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.

    How to fix this

Other fixes

Strengthen the DMARC policyTXT

Rejects mail that fails DMARC, the strongest protection against spoofing. Changes: Subdomains move one step, from sp=quarantine to the domain policy (p=reject).

TypeTXT
Name / Host
_dmarc.grab.co

Some DNS providers want just “_dmarc” here.

Value
v=DMARC1; p=reject; rua=mailto:re+gwftljwbcnk@dmarc.postmarkapp.com; adkim=r; aspf=r
Replaces
v=DMARC1; p=quarantine; pct=100; rua=mailto:re+gwftljwbcnk@dmarc.postmarkapp.com; sp=quarantine; aspf=r;

Publish the MTA-STS recordTXT

Tells sending servers that grab.co publishes an MTA-STS policy at https://mta-sts.grab.co/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT
Name / Host
_mta-sts.grab.co

Some DNS providers want just “_mta-sts” here.

Value
v=STSv1; id=202610040217

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.grab.co. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.

Location
https://mta-sts.grab.co/.well-known/mta-sts.txt
Contents
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
max_age: 604800

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to grab.co, 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.grab.co

  1. Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@grab.co, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.grab.co 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.grab.co

  1. 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://grab.co/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.grab.co with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.