Email authentication check

curiaglobal.com

This check reviews the domain's email authentication setup to help protect against spoofing and phishing.

All data is public, sourced from DNS Last checked about 10 hours ago
Needs attention

curiaglobal.com has email authentication in place, with important improvements still available.

Some protections are present, but tightening the policy, reporting, or sender authorization would improve resilience.

64 out of 110
1 of 4 checks passed
DMARC 34 / 50 · Optional SPF 30 / 30 · Passed BIMI 0 / 20 · Optional TLS 0 / 10 · Optional
Last checked about 10 hours ago
Compare with other domains

DMARC

Optional

Domain-based Message Authentication

34 / 50

Monitor-only policy published

DMARC record is valid and configured correctly.

_dmarc.curiaglobal.com TXT
v=DMARC1; p=none; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected];

Score breakdown

  • DMARC record published +10
  • Syntax valid +5
  • None policy (monitoring only) +4
  • Aggregate reporting (rua) configured and verified +10
  • Failure reporting (ruf) configured +5

Configuration

Policy (p)
none
DKIM alignment (adkim)
Relaxed (default)
SPF alignment (aspf)
Relaxed (default)
Subdomain policy (sp)
Inherits p=none
Failure reporting (fo)
1

Reporting (RUA / RUF)

Aggregate reports Passed
mailto:[email protected]
External domain verification successful
Failure reports Passed
mailto:[email protected]
External domain verification successful
Monitor-only policy (p=none)
This record monitors authentication failures but does not ask receivers to block them, so security scanners and compliance checks often report it as "policy not enabled". Once your reports show legitimate mail is aligned, move to quarantine or reject.
How to fix DMARC policy not enabled

SPF

Passed

Sender Policy Framework

30 / 30

Hard-fail policy, within lookup limits

SPF record is valid and complies with RFC 7208.

curiaglobal.com TXT
v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com -all

Score breakdown

  • SPF record published +10
  • Syntax valid +5
  • Hard fail policy (-all) +10
  • No configuration warnings +5

Configuration

Default policy
-all (hard fail)
DNS lookups
1 / 10 max
Void lookups
0 / 2 max
Syntax check
OK

DNS lookup detail

Each mechanism that may trigger a DNS query at delivery time.

1 include: %{ir}.%{v}.%{d}.spf.has.pphosted.com Macro

Dynamic SPF macro - counts as 1 potential lookup when evaluated at delivery time

SPF macro variables

%{ir} = reversed sender IP address, %{v} = IP version (in-addr/ip6), %{d} = current domain

This mechanism uses SPF macros that are expanded when an email is received. The actual domain queried depends on the sender's IP address and other connection details.

BIMI

Optional

Brand Indicators for Message Identification

0 / 20

No BIMI record published

No BIMI record found for selector 'default'.

Score breakdown

  • BIMI record published (optional) 0 / 5

Configuration

Logo (l)
Not configured
Mark certificate (a)
Not configured
Selector
default
Note
SVG content is not parsed, for safety
BIMI is optional
BIMI usually matters after DMARC enforcement is working. Use it for brand display, not as a replacement for SPF or DMARC.

TLS

Optional

Transport security · MTA-STS & TLS-RPT

0 / 10

Inbound transport protection not fully configured

MTA-STS and TLS-RPT are optional, but they protect inbound mail against transport downgrade attacks and give visibility into TLS delivery failures.

Score breakdown

  • TLS-RPT record configured (optional) 0 / 5
  • MTA-STS policy configured (optional) 0 / 5

Configuration

TLS-RPT
Not configured
MTA-STS
Not configured

Transport checks

TLS-RPT (reporting) Not configured

No TLS-RPT record found.

MTA-STS (policy) Not configured

No MTA-STS record found.

Protect inbound transport

Receiver Shield helps deploy, monitor, and safely enforce MTA-STS and TLS-RPT for curiaglobal.com.

Start monitoring

curiaglobal.com has a DMARC record in monitor-only mode (p=none), which tracks authentication failures without blocking them. SPF is correctly configured with a strict policy (-all), specifying which servers may send on its behalf. A few improvements would strengthen curiaglobal.com's email authentication posture.

Keep curiaglobal.com protected automatically

This check is a snapshot. DNS records drift when providers change, teams edit records, or unauthorized changes slip in. DMARCTrust watches the same authentication layer continuously and tells you when something moves.

DMARC report processing

Aggregate and failure DMARC reports are received, parsed, and turned into sender visibility without manual XML handling.

DNS change alerts

DNS checks run every 5 minutes for monitored domains, with email alerts when DMARC, SPF, BIMI, TLS-RPT, or MTA-STS records change.

Receiver Shield for inbound

Deploy, host, and safely enforce MTA-STS and TLS-RPT when this checker finds an inbound transport gap.

Start monitoring curiaglobal.com View plans First checked about 1 month ago

Check another domain

Run a free email authentication check: DMARC, SPF, BIMI, TLS-RPT, and MTA-STS.

Try a popular example: google.com, amazon.com, booking.com
Explore

How other domains configure email authentication

Showing domains checked by our users. All data is from public DNS records.

Popular domains

Frequently checked

Well configured

Reject policy + valid SPF

Same policy

Also using none

What we check

DMARC policy and alignment, SPF record and includes, BIMI logo and certificate, and inbound transport security with MTA-STS and TLS-RPT.

Why it matters

Healthy authentication improves delivery and blocks spoofing. Major inbox providers increasingly expect DMARC and aligned SPF or DKIM from senders.

What you get

Syntax, policy, reporting validation, include analysis, alignment interpretation, and clear setup guidance for every result.