allegro.pl
Good, with 2 things to fix
allegro.pl scored 84/100 (grade B). The main issues are DKIM key shorter than 2048 bits and no DMARC aggregate report address. Detected senders: Google Workspace and Salesforce.
Checked 2026-10-04 02:15 UTC · fresh check
Set up a DMARC report address
Without a rua address nobody receives aggregate reports, so you cannot see who sends as allegro.pl or tell when it is safe to tighten the policy. Adding reporting does not change how receivers treat your mail.
Applies to: _dmarc.allegro.pl
- Get an address that collects DMARC aggregate reports: add allegro.pl to MailVakt to receive one, or sign up with any DMARC report service. 2. Edit the TXT record at _dmarc.allegro.pl and add rua=mailto:<that address>, keeping every other tag (p=quarantine) as it is. 3. A report service on another domain must authorize allegro.pl; most publish that record for you.
All checks
MXCan servers find your inbox?Only one MX hostInfo
- Info: Only one MX host
All mail for allegro.pl goes to allegro.in.tmes.trendmicro.eu. Most hosted providers make that one name highly available; if you run your own server, consider a backup MX.
SPFWho may send as you?No issues foundPass
Nothing to report.
DKIMAre your emails signed?DKIM key shorter than 2048 bitsNeeds attention
- Warning: DKIM key shorter than 2048 bits
google (1024-bit) uses an RSA key below 2048 bits. Short keys can be factored and some receivers treat them as weak. Rotate to a 2048-bit key at your sending provider.
- Pass: DKIM key published
allegro.pl publishes a DKIM key under google.
DMARCWhat happens to fakes?No DMARC aggregate report addressNeeds attention
- Warning: No DMARC aggregate report address
Without a rua address you receive no aggregate reports, so you cannot see who sends as your domain or safely tighten the policy.
How to fix this - 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 issues foundPass
Nothing to report.
MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
- Info: No MTA-STS record
No MTA-STS record at _mta-sts.allegro.pl. 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.allegro.pl. 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. There is no report address yet: set one up first (see the DMARC reporting fix) so you can confirm your legitimate mail passes before enforcing.
_dmarc.allegro.pl
Some DNS providers want just “_dmarc” here.
v=DMARC1; p=reject; adkim=r; aspf=r
v=DMARC1; p=quarantine; adkim=r; aspf=r; rf=afrf;
Publish the MTA-STS recordTXT
Tells sending servers that allegro.pl publishes an MTA-STS policy at https://mta-sts.allegro.pl/.well-known/mta-sts.txt. Change the id whenever the policy file changes.
_mta-sts.allegro.pl
Some DNS providers want just “_mta-sts” here.
v=STSv1; id=202610040215
Host the MTA-STS policy filepolicy-file
Serve this file over HTTPS with a valid certificate for mta-sts.allegro.pl. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.
https://mta-sts.allegro.pl/.well-known/mta-sts.txt
version: STSv1 mode: testing mx: allegro.in.tmes.trendmicro.eu max_age: 604800
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to allegro.pl, 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.allegro.pl
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@allegro.pl, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.allegro.pl with the value v=TLSRPTv1; rua=mailto:<that address>.