Running your DNS diagnostic…
Checking SPF, DMARC, DKIM, MX, DNS, blacklists and domain & SSL expiry. A domain we haven't scanned before takes a few seconds — hang tight.
Checking SPF, DMARC, DKIM, MX, DNS, blacklists and domain & SSL expiry. A domain we haven't scanned before takes a few seconds — hang tight.
Scanned Aug 30, 2026 22:28 UTC · 7 checks · public report
One finding blocks deliverability.
auth.braka-ai.de publishes DMARC with p=none — spoofed mail is monitored but not blocked.
Your domain does not have an SPF record published in DNS. SPF helps mail servers check whether messages sent from your domain are coming from approved senders, which can reduce spoofing and improve deliverability. To fix this, add an SPF record for the domain that lists the mail services you use to send email.
Your domain has a DMARC setting, but it is only in monitoring mode, so it is not actually blocking fake or forged emails. This matters because attackers can still send messages that look like they came from your domain, which can hurt trust and increase phishing risk. To fix it, change the DMARC policy from monitoring only to an enforcing mode so email receivers are told to reject or quarantine suspicious mail.
One send: the full report — every finding and fix — lands in your inbox, with a free account waiting. Opening it signs you in and starts a 14-day Monitor trial. No card, and you can unsubscribe in one click.
Domain owner? Re-scan any time — or email [email protected] to have this page removed.
v=DMARC1; p=none;_dmarc · Record type: TXT · TTL: 3600v=DMARC1; p=quarantine; np=rejectThis domain does not have mail-handling records set up, so email sent to it cannot be delivered. That matters because people and services trying to email you will get failures or bounced messages. To fix it, add the proper mail server routing records for the domain so incoming email knows where to go.