Detection, Analysis & Prevention Tool (Node.js Edition)
Educational Project | Server: rilzacosmetics.com (185.73.8.3)
Sends with custom From headers via nodemailer's sendmail transport (equivalent to PHP's /sbin/sendmail -t). Emails originate from this server (rilzacosmetics.com).
Click to auto-fill the form with test data:
Paste raw email headers from Gmail ("Show Original") or any email client to analyze for spoofing indicators.
These emails were sent from the server (rilzacosmetics.com / 185.73.8.3) using /sbin/sendmail. Each test demonstrates a different spoofing scenario and how email authentication handles it.
| Test | From (Header) | Actual Server | SPF | DKIM | DMARC | Result |
|---|---|---|---|---|---|---|
| 1. Legitimate | info@rilzacosmetics.com | rilzacosmetics.com | PASS | PASS | PASS | Inbox |
| 2. Spoofed | hasan@cresttower.com | rilzacosmetics.com | FAIL | FAIL | FAIL | Spam + Warning |
| 3. Blocked | security@hbl.com | rilzacosmetics.com | FAIL | FAIL | REJECT | Blocked |
| 4. Blocked | info@uspto.gov | rilzacosmetics.com | FAIL | FAIL | REJECT | Blocked |
Spoofed email gets delivered but goes to Spam with warning. Domain owner gets no rejection enforcement. Example: cresttower.com
Spoofed email is quarantined (usually Spam folder). Receiver gets a warning. Better than none, but not fully protected.
Spoofed email is completely rejected. Never delivered. Maximum protection. Example: hbl.com, uspto.gov
Email spoofing is the creation of email messages with a forged sender address. Because core email protocols (SMTP) do not have a built-in authentication mechanism, it is possible to send an email that appears to come from any address.
Attacker's Server (rilzacosmetics.com / 185.73.8.3)
|
| SMTP Connection to Gmail
| MAIL FROM: <info@rilzacosmetics.com> ← Envelope (hidden from user)
|
| Headers in email:
| From: USPTO <info@uspto.gov> ← FAKE! (what user sees)
| Subject: Important Notice
|
v
Gmail Server (mx.google.com)
|
| Checks SPF: Is 185.73.8.3 authorized for uspto.gov? NO → FAIL
| Checks DKIM: Is email signed by uspto.gov? NO → FAIL
| Checks DMARC: What is uspto.gov's policy? p=reject → BLOCK
|
v
EMAIL REJECTED - Never delivered to user
SPF allows domain owners to specify which mail servers are authorized to send emails on behalf of their domain.
rilzacosmetics.com TXT "v=spf1 ip4:185.73.8.3 include:spf.hostns.io +a +mx -all"v=spf1 | SPF version 1 |
ip4:185.73.8.3 | Allow this specific IP to send mail |
include:spf.hostns.io | Also allow IPs listed by hosting provider |
+a | Allow IPs in A record |
+mx | Allow IPs in MX record |
-all | Reject all others (strict) |
DKIM adds a digital signature to outgoing emails. The receiver verifies this signature using the sender's public key published in DNS.
default._domainkey.rilzacosmetics.com TXT "v=DKIM1; k=rsa; p=MIIBIjAN..."DMARC ties SPF and DKIM together and tells receivers what to do when authentication fails.
_dmarc.rilzacosmetics.com TXT "v=DMARC1; p=none; rua=mailto:info@rilzacosmetics.com"| Policy | Action | Protection Level |
|---|---|---|
p=none | Monitor only - no action taken | Low (spoofed emails still delivered) |
p=quarantine | Send to Spam/Junk folder | Medium (spoofed emails in spam) |
p=reject | Reject/Block completely | High (spoofed emails never delivered) |
| Domain | DMARC Policy | Effect on Spoofing |
|---|---|---|
| rilzacosmetics.com | p=none | Spoofed emails monitored but delivered |
| cresttower.com | p=none (or absent) | Spoofed emails land in Spam with warning |
| hbl.com | p=reject | Spoofed emails completely blocked |
| uspto.gov | p=reject | Spoofed emails completely blocked + reported to DHS |
ATTACKER EMAIL SERVER VICTIM | | | | 1. Connects to SMTP server | | | 2. Sets MAIL FROM (envelope) | | | 3. Sets fake From: header | | | 4. Sends email | | |----------------------------------->| | | | 5. Checks SPF | | | IP authorized? NO | | | 6. Checks DKIM | | | Valid signature? NO | | | 7. Checks DMARC | | | Policy? | | | | | IF p=none: | 8a. Deliver to Spam | | |------------------------------->| Warning shown | | | | IF p=reject: | 8b. REJECT - Email blocked | | |----X | Protected! | | | | IF legitimate: | 8c. Deliver to Inbox | | |------------------------------->| Clean email
Email Spoofing Lab (Node.js Edition) — Educational Project
Server: rilzacosmetics.com | IP: 185.73.8.3
Built for cybersecurity education purposes only.