All data shown is public and sourced from DNS.
Last checked about 8 hours ago
telekom.de domain score
Your domain has basic email authentication in place. Consider strengthening your configuration for better protection.
Top Recommendation
Upgrade DMARC policy to reject for stronger protection
DMARC improvement
telekom.de has a DMARC quarantine policy, directing unauthenticated emails to spam. SPF is published with a soft fail policy (~all), flagging unauthorized senders without blocking them. A few improvements would strengthen telekom.de's email authentication posture.
Curious how this compares? See the DMARC posture of the top 100 domains.
DMARC Check Results
42 / 50 points
Score Breakdown
DMARC check passed: properly configured
DMARC record is valid and configured correctly.
_dmarc.telekom.de TXT Entry:
v=DMARC1;p=quarantine;rua=mailto:[email protected];ruf=mailto:[email protected];
Policy (p)
quarantine
DKIM Alignment (adkim)
Relaxed (default)
SPF Alignment (aspf)
Relaxed (default)
Reporting (RUA/RUF)
Add Our Monitoring System
You can add our monitoring system alongside your existing setup. DMARC supports multiple mailto: addresses, giving you additional visibility and backup reporting.
- Automated DMARC report processing every 5 minutes
- Track all sending sources and authentication results
- Email alerts when your DNS records change
BIMI Check (default selector)
0 / 20 points
Score Breakdown
No BIMI Record Found
Publish a TXT record at default._bimi.telekom.de with v=BIMI1, logo URL (l=) and optional verified mark certificate (a=).
SPF Record Check Results
26 / 30 points
Score Breakdown
SPF record is valid.
telekom.de TXT SPF Entry:
v=spf1 include:_spfa.telekom.com ~all
Syntax Check
OK
DNS Lookup Count
8 / 10 max
Root-level mechanisms requiring DNS queries: 1.
Void Lookups
0 / 2 max
Default Policy
~allSoft fail: Mark emails from unauthorized servers as suspicious but don't reject
All Authorized IP Addresses
Grouped by DNS record source (includes and sub-includes)
include:_spfa.telekom.com
This record also contains:
include:_spft.telekom.com
include:spf.protection.outlook.com | Microsoft 365
include:_spf.google.com | Google
include:amazonses.com | Amazon SES
DNS Lookup Details
include:
_spfa.telekom.com
SPF record found
telekom.de
TXT Record
v=spf1 include:_spft.telekom.com ip4:80.149.170.246 include:spf.protection.outlook.com include:_spf.google.com include:amazonses.com include:_spf.salesforce.com ~all
Processed recursively per RFC 7208
include:
_spft.telekom.com
SPF record found
_spfa.telekom.com
TXT Record
v=spf1 ip4:194.25.225.128/26 ip4:194.25.225.192/26 ip4:80.158.70.128/30 exists:%{i}.spf.telekom.com ~all
Processed recursively per RFC 7208
exists:
%{i}.spf.telekom.com
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.
include:
spf.protection.outlook.com
| Microsoft 365
SPF record found
_spfa.telekom.com
TXT Record
v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 -all
Processed recursively per RFC 7208
include:
_spf.google.com
| Google
SPF record found
_spfa.telekom.com
TXT Record
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
include:
amazonses.com
| Amazon SES
SPF record found
_spfa.telekom.com
TXT Record
v=spf1 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 ip4:23.249.208.0/20 ip4:23.251.224.0/19 ip4:76.223.176.0/20 ip4:54.240.64.0/18 ip4:76.223.128.0/19 ip4:216.221.160.0/19 ip4:206.55.144.0/20 ip4:24.110.64.0/18 -all
Processed recursively per RFC 7208
include:
_spf.salesforce.com
SPF record found
_spfa.telekom.com
TXT Record
v=spf1 exists:%{i}._spf.mta.salesforce.com -all
Processed recursively per RFC 7208
exists:
%{i}._spf.mta.salesforce.com
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.
TLS Security
5 / 10 points
Score Breakdown
TLS-RPT (Reporting)
TLS-RPT Reporting Configured
Current TLS-RPT Entry:
v=TLSRPTv1; rua=mailto:[email protected];
Reporting URIs:
mailto:[email protected]
MTA-STS (Policy)
MTA-STS Not Configured
Publish a TXT record at _mta-sts.telekom.de with v=STSv1 and policy ID (id=).
Protect inbound transport
You've checked your outbound authentication. But without MTA-STS and TLS-RPT, mail delivered to telekom.de isn't protected against transport downgrade attacks. Receiver Shield helps you deploy, monitor, and safely enforce transport security.
Know when your DNS records change
The check you just ran shows your current configuration. But DNS records change, sometimes without you knowing. A well-meaning IT change, a third-party provider update, or an unauthorized modification can break your email delivery overnight.
Configuration Drift
IT changes that accidentally break authentication
Provider Updates
Third-party services changing their SPF includes
Unauthorized Changes
Attackers modifying records to send as you
DMARCTrust monitors your DNS records continuously. When something changes, you get an email alert with exactly what changed and why it matters. No more surprises when customers complain their emails bounced.
Check Another Domain
Run a free email authentication check (DMARC, SPF, BIMI).
We will generate a shareable URL for your domain.
Try popular examples: google.com, amazon.com, booking.com
Explore other domains
Discover how other organizations configure their email authentication
Popular Domains
Frequently checked
Well-Configured
Reject policy + valid SPF
Same Policy
Also using quarantine
Showing domains checked by our users. All data is from public DNS records.
About This Checker
What we check
We analyze your domain's email authentication: DMARC policy and alignment, SPF record and includes, and BIMI logo and certificate status when present.
Why it matters
Healthy authentication improves delivery and blocks spoofing. Major inbox providers increasingly expect DMARC and aligned SPF/DKIM from senders.
Included features
- DMARC syntax, policy, and reporting validation
- SPF record evaluation and include analysis
- DKIM/SPF alignment interpretation
- BIMI record and VMC detection
- Clear setup and remediation guidance
Monitor your email authentication 24/7
This check shows a snapshot. With DMARCTrust, you get continuous monitoring of your DMARC reports and DNS records, with instant alerts when something changes.