diff --git a/web/src/lib/components/BimiRecordDisplay.svelte b/web/src/lib/components/BimiRecordDisplay.svelte new file mode 100644 index 0000000..0d7a1b9 --- /dev/null +++ b/web/src/lib/components/BimiRecordDisplay.svelte @@ -0,0 +1,77 @@ + + +{#if bimiRecord} +
+ BIMI allows your brand logo to be displayed next to your emails in supported mail + clients. Requires strong DMARC enforcement (quarantine or reject policy) and + optionally a Verified Mark Certificate (VMC). +
+ +{bimiRecord.selector}
+ Domain: {bimiRecord.domain}
+ {bimiRecord.record}
+ DKIM cryptographically signs your emails, proving they haven't been tampered with in transit. Receiving servers verify this signature against your DNS records.
+{dkim.selector}
+ Domain: {dkim.domain}
+ {dkim.record}
+ DMARC builds on SPF and DKIM by telling receiving servers what to do with emails that fail authentication checks. It also enables reporting so you can monitor your email security.
++ DMARC builds on SPF and DKIM by telling receiving servers what to do with emails + that fail authentication checks. It also enables reporting so you can monitor your + email security. +
+ +p=reject for maximum protection.
+ Once you've validated your configuration and ensured all legitimate mail
+ passes, consider upgrading to p=reject for maximum protection.
p=quarantine or p=reject to actively protect your domain.
+ After monitoring reports, upgrade to p=quarantine or
+ p=reject to actively protect your domain.
sp={dmarcRecord.policy} to match your main policy for consistent protection.
+ Weaker subdomain protection — consider setting
+ sp={dmarcRecord.policy} to match your main policy for consistent
+ protection.
{dmarcRecord.policy}) which provides consistent protection.
+ Good default — subdomains inherit the main policy ({dmarcRecord.policy}) which provides consistent protection.
pct=100 once you've validated your configuration.
+ Partial enforcement — only {dmarcRecord.percentage}% of
+ messages are subject to DMARC policy. Consider increasing to
+ pct=100 once you've validated your configuration.
pct=100 for full protection.
+ Low enforcement — only {dmarcRecord.percentage}% of
+ messages are protected. Gradually increase to pct=100 for full
+ protection.
aspf=s) once your sending domains are standardized.
+ For maximum brand protection, consider strict alignment (aspf=s) once your sending domains are standardized.
adkim=s) once your sending domains are standardized.
+ For maximum brand protection, consider strict alignment (adkim=s) once your sending domains are standardized.
{dmarcRecord.record}
SPF specifies which mail servers are authorized to send emails on behalf of your domain. Receiving servers check the sender's IP address against your SPF record to prevent email spoofing.
-{spf.domain}
- {#if index > 0}
- Included
- {/if}
- {spf.record}
- DKIM cryptographically signs your emails, proving they haven't been tampered with in transit. Receiving servers verify this signature against your DNS records.
-{dkim.selector}
- Domain: {dkim.domain}
- {dkim.record}
- BIMI allows your brand logo to be displayed next to your emails in supported mail clients. Requires strong DMARC enforcement (quarantine or reject policy) and optionally a Verified Mark Certificate (VMC).
-{dnsResults.bimi_record.selector}
- Domain: {dnsResults.bimi_record.domain}
- {dnsResults.bimi_record.record}
- {description}
{/if} diff --git a/web/src/lib/components/SpfRecordsDisplay.svelte b/web/src/lib/components/SpfRecordsDisplay.svelte new file mode 100644 index 0000000..172e9f7 --- /dev/null +++ b/web/src/lib/components/SpfRecordsDisplay.svelte @@ -0,0 +1,69 @@ + + +{#if spfRecords && spfRecords.length > 0} +SPF specifies which mail servers are authorized to send emails on behalf of your domain. Receiving servers check the sender's IP address against your SPF record to prevent email spoofing.
+{spf.domain}
+ {#if index > 0}
+ Included
+ {/if}
+ {spf.record}
+