Email authentication check

allegro.pl

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

allegro.pl 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.

77 out of 110
2 of 4 checks passed
DMARC 27 / 50 · Optional SPF 30 / 30 · Passed BIMI 20 / 20 · Passed TLS 0 / 10 · Optional
Last checked 1 day ago
Compare with other domains

DMARC

Optional

Domain-based Message Authentication

27 / 50

Valid policy without aggregate reporting

DMARC record is valid but no reporting email is configured.

_dmarc.allegro.pl TXT
v=DMARC1; p=quarantine; adkim=r; aspf=r; rf=afrf;

Score breakdown

  • DMARC record published +10
  • Syntax valid +5
  • Quarantine policy +12
  • Aggregate reporting (rua) not configured 0 / 10
  • Failure reporting (ruf) not configured (optional) 0 / 5

Configuration

Policy (p)
quarantine
DKIM alignment (adkim)
Relaxed (r)
SPF alignment (aspf)
Relaxed (r)
Subdomain policy (sp)
Inherits p=quarantine

Reporting (RUA / RUF)

Aggregate reports Failed
Not configured
Required for aggregate visibility
Failure reports Optional
Not configured
Optional failure reporting is not configured
Record uses tags removed by RFC 9989
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.

allegro.pl TXT
v=spf1 include:_spf.google.com include:spf.tmes.trendmicro.eu include:_spf.salesforce.com ip4:193.23.48.0/24 ip4:193.203.222.0/23 ip4:194.0.251.0/24 ip4:91.194.188.0/23 ip4:91.207.14.0/23 ip4:178.21.152.0/21 ip4:5.134.208.0/21 ip4:185.31.24.0/22 -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
4 / 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: _spf.google.com Valid

SPF record found

v=spf1 ip4:74.125.0.0/16 ip4:209.85.128.0/17 ip6:2001:4860:4864::/56 ip6:2404:6800:4864::/56 ip6:2607:f8b0:4864::/56 ip6:2800:3f0:4864::/56 ip6:2a00:1450:4864::/56 ip6:2c0f:fb50:4864::/56 ~all

Processed recursively per RFC 7208

2 include: spf.tmes.trendmicro.eu Valid

SPF record found

v=spf1 ip4:18.185.115.0/25 ip4:18.185.115.128/26 ip4:34.253.238.128/26 ip4:34.253.238.192/26 ip4:3.72.196.143 ip4:18.156.0.20 ip4:35.156.245.132 ip4:18.208.22.124 ip4:18.208.22.125 ip4:18.96.32.128/27 ip6:2a05:d014:10e:d900::/60 ~all

Processed recursively per RFC 7208

3 include: _spf.salesforce.com Valid

SPF record found

v=spf1 exists:%{i}._spf.mta.salesforce.com -all

Processed recursively per RFC 7208

4 exists: %{i}._spf.mta.salesforce.com Macro

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

SPF macro variables

%{i} = sender IP address

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.

Authorized IP addresses

allegro.pl

193.23.48.0/24 193.203.222.0/23 194.0.251.0/24 91.194.188.0/23 91.207.14.0/23 178.21.152.0/21 5.134.208.0/21 185.31.24.0/22

This record also contains

include:_spf.google.com include:spf.tmes.trendmicro.eu include:_spf.salesforce.com

include:_spf.google.com

74.125.0.0/16 209.85.128.0/17 2001:4860:4864::/56 2404:6800:4864::/56 2607:f8b0:4864::/56 2800:3f0:4864::/56 2a00:1450:4864::/56 2c0f:fb50:4864::/56

include:spf.tmes.trendmicro.eu

18.185.115.0/25 18.185.115.128/26 34.253.238.128/26 34.253.238.192/26 3.72.196.143 18.156.0.20 35.156.245.132 18.208.22.124 18.208.22.125 18.96.32.128/27 2a05:d014:10e:d900::/60

BIMI

Passed

Brand Indicators for Message Identification

20 / 20

Verified logo configured

BIMI record validated

default._bimi.allegro.pl TXT
v=BIMI1; l=https://allegro.pl/allegro-bimi.svg; a=https://allegro.pl/allegro-bimi.pem;

Score breakdown

  • BIMI record published +5
  • BIMI record valid +5
  • Logo URL accessible and valid SVG +5
  • Verified Mark Certificate (VMC) valid +5

Configuration

Logo (l)
image/svg+xml
Mark certificate (a)
Valid PEM detected
Selector
default
Note
SVG content is not parsed, for safety

Assets

Logo URL
https://allegro.pl/allegro-bimi.svg
Valid
Mark certificate
https://allegro.pl/allegro-bimi.pem
Valid

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 allegro.pl.

Start monitoring

allegro.pl has a DMARC record but no reporting configured, limiting visibility into authentication results. SPF is correctly configured with a strict policy (-all), specifying which servers may send on its behalf. A few improvements would strengthen allegro.pl's email authentication posture.

Keep allegro.pl 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 allegro.pl View plans First checked 7 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

Same policy

Also using quarantine

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.