The Email Stack Scan a domain
← Domain reports

oscar.comemail setup

Public DNS report for oscar.com, read on September 27, 2026: authentication, the email tools its records reveal, the sender rules it meets, and what would raise its score. Every line is a public record.

This page is a snapshot from our index. Re-run to read DNS as it is right now, or type any other domain.

The Email StackPublic DNS Report
Report
TES-20260927-8B597B
Read
27 Sept 2026, 12:53 UTC
Source
Index snapshot
Domain

oscar.com

No DMARC policy. Anyone can send as this domain and most inboxes will accept it.

2 of 8 checks pass · 1 tool visible in DNS · 1 urgent fix

F 30/100 Grade F
SPFValid, soft fail20/20
DKIMNo common selector found0/15
DMARCNo record0/30
MX2 hosts10/10
MTA-STSNot published0/10
TLS-RPTNot published0/5
BIMINot published0/5
DNSSECNot signed0/5

1 · Authentication and transport

SPF

PassValid, soft fail

Anything not on the list is accepted but marked. Google recommends ~all; with DMARC enforced it is as strong as -all.

v=spf1 ip4:208.97.70.202 ip4:75.126.208.140 ip4:75.126.197.11 ip4:205.234.170.144 ip4:205.234.170.134 ip4:216.16.247.122 mx ~all

DKIM

ReviewNo common selector found

None of the common selector names we probe published a key. The domain may use a custom selector; check a real message's DKIM-Signature header.

DMARC

FailNo record

Receivers have no instruction for mail that fails SPF and DKIM, so spoofed mail is a judgement call.

MX

Pass2 hosts

More than one receiving server, so a single outage does not bounce mail.

10 mxa-0029cf01.gslb.pphosted.com
20 mxb-0029cf01.gslb.pphosted.com

MTA-STS

ReviewNot published

Sending servers cannot tell that this domain requires TLS, so inbound mail can be downgraded to plain text by anyone on the path.

TLS-RPT

OptionalNot published

Nobody is told when TLS to this domain fails. Cheap to add once MTA-STS is in place.

BIMI

OptionalNot published

Optional, and it requires DMARC at quarantine or reject first.

DNSSEC

OptionalNot signed

Optional. Signing the zone protects every record in this report from tampering.

2 · Tools visible in DNS

LayerToolEvidence
GatewayProofpointMX mxa-0029cf01.gslb.pphosted.com

Only tools that leave a DNS trace appear. A shared DKIM selector is attributed only when its CNAME target names the vendor.

3 · Sender requirements (Google, Yahoo, Microsoft)

RequirementApplies toStatusNote
Authenticate with SPF or DKIMGoogleYahooMicrosoftVerifiedAt least one method is in place.
Bulk senders: both SPF and DKIMGoogleYahooMissingDKIM could not be confirmed from DNS.
Publish a DMARC record (p=none is enough)GoogleYahooMicrosoftMissingNo _dmarc record.
From: domain aligns with SPF or DKIMGoogleYahooMicrosoftNot checkable hereNeeds a real message. The Send-a-Test report will check this.
Valid forward and reverse DNS for sending IPsGoogleYahooNot checkable hereDepends on the sending server, not the domain.
Encrypt in transit (TLS)GoogleYahooNot checkable hereOutbound TLS depends on your sending tool; MTA-STS would cover inbound.
One-click unsubscribe (RFC 8058) for marketing mailGoogleYahooNot checkable hereA message header, not a DNS record. Microsoft recommends it rather than requiring it.
Spam complaint rate under 0.1% (0.3% is the hard limit)GoogleYahooNot checkable hereRead it in Google Postmaster Tools and Yahoo Sender Hub. Google’s target is 0.1%; 0.3% is where enforcement starts.

4 · What to fix, in order

  1. P1

    Publish a DMARC record

    Google, Yahoo and Microsoft all require one. Start in monitor mode and collect reports. The rua address must exist; an alias or a free reporting service is fine.

    Publish at_dmarc.oscar.com
    v=DMARC1; p=none; rua=mailto:dmarc@oscar.com; fo=1
  2. P2

    Turn on DKIM signing in every sending tool

    Each tool that sends for you has a DKIM setup page that gives you the record to publish.

    Publish at<selector>._domainkey.oscar.com
  3. P3

    Publish MTA-STS (record and policy file)

    Tells sending servers to require TLS to your MX hosts, which prevents downgrade attacks. The TXT record alone does nothing: the policy file must be served over HTTPS at mta-sts.oscar.com. Start in testing mode, watch TLS-RPT, then switch to enforce.

    Publish at_mta-sts.oscar.com and https://mta-sts.oscar.com/.well-known/mta-sts.txt
    TXT  v=STSv1; id=2026100401

mta-sts.txt:
version: STSv1
mode: testing
mx: mxa-0029cf01.gslb.pphosted.com
mx: mxb-0029cf01.gslb.pphosted.com
max_age: 86400
  4. P3

    Publish TLS-RPT

    You get a report when TLS delivery to your domain fails; this is what notices a downgrade that MTA-STS is meant to prevent. The address must exist.

    Publish at_smtp._tls.oscar.com
    v=TLSRPTv1; rua=mailto:tls-rpt@oscar.com
  5. P3

    Sign the zone with DNSSEC

    Protects every record in this report from being swapped in transit. Two steps: enable signing at your DNS host (one switch at Cloudflare and most others), then add the DS record it gives you at your registrar.

    Publish atoscar.com

Appendix · Raw DNS answers

NameTypeAnswer
oscar.comMX10 mxa-0029cf01.gslb.pphosted.com
20 mxb-0029cf01.gslb.pphosted.com
oscar.comA13.227.249.110
13.227.249.49
13.227.249.69
13.227.249.67
oscar.comTXTv=spf1 ip4:208.97.70.202 ip4:75.126.208.140 ip4:75.126.197.11 ip4:205.234.170.144 ip4:205.234.170.134 ip4:216.16.247.122 mx ~all
_dmarc.oscar.comTXTno record
<selector>._domainkey.oscar.comTXTno record
_mta-sts.oscar.comTXTno record
_smtp._tls.oscar.comTXTno record
default._bimi.oscar.comTXTno record

How to verify this yourself. Every line above comes from public DNS. Run dig TXT _dmarc.oscar.com or dig MX oscar.com and compare. Method: theemailstack.com/methodology.

Scores weigh SPF 20, DKIM 15, DMARC 30, MX 10, MTA-STS 10, TLS-RPT 5, BIMI 5, DNSSEC 5. Message-level requirements (alignment, unsubscribe headers, complaint rate) are not checkable from DNS and are marked as such, never guessed.

Scan to re-run livetheemailstack.com/report/oscar.com

About this report

The Email Stack reads public DNS for well-known domains and publishes the result as a report, the same one anyone can generate for any domain at /report. It is a point-in-time read: records change, and a domain that scores F today may score differently next month. The "Re-run live" button reads DNS again in your browser.

Scores weigh SPF 20, DKIM 15, DMARC 30, MX 10, MTA-STS 10, TLS-RPT 5, BIMI 5 and DNSSEC 5. Tools are named only when a DNS record names the vendor; a shared DKIM selector counts only when its CNAME target does. Message-level requirements such as alignment and one-click unsubscribe cannot be read from DNS and are marked as such, never guessed. Method: how we detect tools.

Own this domain and see something wrong? DNS is the source; fix the record and the next read will show it. Questions to hello@theemailstack.com.