Core Concepts

Understanding the fundamentals of email security and how the ReputeAPI works.

Overview

This section covers the core concepts you need to understand to effectively use the ReputeAPI and improve your domain's email security.

Topics Covered

Why Email Security Matters

Email is the most common attack vector for phishing, spoofing, and business email compromise (BEC). Proper email security configuration:

✅ Prevents Spoofing - Stops attackers from impersonating your domain ✅ Builds Trust - Improves email deliverability and sender reputation ✅ Protects Brand - Prevents your domain from being used in phishing attacks ✅ Meets Compliance - Satisfies security and privacy requirements

The Three Pillars

Email security is built on three complementary standards:

1. SPF (Sender Policy Framework)

Defines which mail servers are authorized to send email for your domain.

example.com. IN TXT "v=spf1 include:_spf.google.com -all"

2. DKIM (DomainKeys Identified Mail)

Adds cryptographic signatures to emails to verify authenticity and detect tampering.

selector._domainkey.example.com. IN TXT "v=DKIM1; k=rsa; p=MIGfMA..."

3. DMARC (Domain-based Message Authentication)

Tells receiving servers what to do with emails that fail SPF or DKIM checks.

_dmarc.example.com. IN TXT "v=DMARC1; p=reject; rua=mailto:dmarc@example.com"

How They Work Together

graph LR
    A[Incoming Email] --> B{SPF Check}
    B --> C{DKIM Check}
    C --> D{DMARC Check}
    D -->|Pass| E[Deliver to Inbox]
    D -->|Fail + p=reject| F[Reject Email]
    D -->|Fail + p=quarantine| G[Mark as Spam]
    D -->|Fail + p=none| H[Deliver + Report]
  1. SPF verifies the sending server is authorized
  2. DKIM verifies the email hasn't been modified
  3. DMARC checks alignment and enforces policy

Next Steps