Email authentication check

meo.pt

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 1 day ago
Needs attention

meo.pt 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.

72 out of 110
1 of 4 checks passed
Last checked 1 day ago
Compare with other domains

DMARC

Optional

Domain-based Message Authentication

42 / 50

Quarantine policy enabled

DMARC record is valid and configured correctly.

_dmarc.meo.pt TXT
v=DMARC1; p=quarantine; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]; sp=quarantine; fo=1; rf=afrf

Score breakdown

  • DMARC record published +10
  • Syntax valid +5
  • Quarantine policy +12
  • Aggregate reporting (rua) configured and verified +10
  • Failure reporting (ruf) configured +5

Configuration

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

Reporting (RUA / RUF)

Aggregate reports Passed
External domain verification successful
Failure reports Passed
External domain verification successful
Record uses tags removed by RFC 9989
RFC 9989 (May 2026) removed the pct tag. Use t=y for staged rollouts instead. RFC 9989 (May 2026) removed the rf tag. Only one format (afrf) was ever defined.

SPF

Passed

Sender Policy Framework

30 / 30

Hard-fail policy, within lookup limits

SPF record is valid and complies with RFC 7208.

meo.pt TXT
v=spf1 ip4:62.28.27.36 ip4:62.28.27.37 ip4:62.48.208.146 ip4:62.48.208.147 ip4:185.17.230.232 ip4:185.17.230.233 ip4:62.28.206.90 ip4:83.240.175.147 ip4:83.240.183.5 ip4:83.240.183.6 ip4:83.240.183.2 ip4:83.240.183.3 include:_spfrlo.meoempresas.pt -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: _spfrlo.meoempresas.pt Valid

SPF record found

v=spf1 ip4:62.28.164.246 ip4:62.28.164.247 ip4:62.28.164.248 ip4:62.28.164.249 ip4:62.28.164.250 ip4:62.28.164.251 ip4:62.28.164.253 ip4:83.240.148.148 ip4:83.240.148.149 -all

Processed recursively per RFC 7208

Authorized IP addresses

meo.pt

62.28.27.36 62.28.27.37 62.48.208.146 62.48.208.147 185.17.230.232 185.17.230.233 62.28.206.90 83.240.175.147 83.240.183.5 83.240.183.6 83.240.183.2 83.240.183.3

This record also contains

include:_spfrlo.meoempresas.pt

include:_spfrlo.meoempresas.pt

62.28.164.246 62.28.164.247 62.28.164.248 62.28.164.249 62.28.164.250 62.28.164.251 62.28.164.253 83.240.148.148 83.240.148.149

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 meo.pt.

Start monitoring

meo.pt has a DMARC quarantine policy, directing unauthenticated emails to spam. SPF is correctly configured with a strict policy (-all), specifying which servers may send on its behalf. A few improvements would strengthen meo.pt's email authentication posture.

Keep meo.pt 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 meo.pt View plans First checked 5 months 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

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.