Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Washingtonpost

washingtonpost.com
🏆Rank #350 🏷 Media 🇺🇸United States

Washingtonpost uses Iterable for marketing email and Amazon SES for transactional/notifications. They rank #350 in the Tranco list of most-popular domains. Email goes out from 4 different subdomains. Their email authentication setup is solid (score 100/100).

Marketing ESPIterable
Transactional ESPAmazon SES
Total observations50
Active days21
Avg per active day2.4
Last activity📬 Active · today
Cadence~every 3 days
Compare Washingtonpost with another brand:

Email setup 100/100

Authentication signals observed in this brand's emails. SPF, DKIM and DMARC are the standard sender-authentication stack — see the DMARC policy below for whether spoofing is actually blocked or just monitored. One-click unsubscribe meets Google & Yahoo's bulk-sender requirements.

Strong email setup
Authentication is in good shape — SPF, DKIM, and DMARC enforcement all configured.
100/100
SPF
pass
DKIM
pass
DMARC
pass (reject)
BIMI
verified VMC
Unsubscribe
one-click
SPF lookups 5/10

SPF / DKIM / DMARC above reflect the last 10 emails we've observed. DMARC policy is read live from DNS.

Authentication

DMARC reports sent to Validity (EmailAnalyst). Policy p=reject means receivers actively block or quarantine spoofed mail.

SPF alignment: all 35 observed emails use a return-path aligned with washingtonpost.com (bounces.washingtonpost.com, us-west-2.washingtonpost.com, email.washingtonpost.com). SPF authenticates the visible From — supports DMARC directly.

DKIM alignment: all 39 observed emails sign with a domain aligned with washingtonpost.com (nl.mail.washingtonpost.com, washingtonpost.com, e.mail.washingtonpost.com). DKIM authenticates the visible From — supports DMARC directly.

Transport & deliverability

Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 3 sends).

Other ESPs detected

Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).

None — only the primary ESP(s) shown above

Confirmed senders

ESPs we've seen sending email for this brand. Green = confirmed by SPF, sender IP rDNS, or known infra pairing (label shows the source). Grey = observed but not yet confirmed by SPF or PTR.

Amazon SES ✓ confirmed Iterable ✓ via SparkPost

Other SPF authorizations

ESPs this brand has authorized in their SPF record. We confirm them with a green ✓ only after seeing recurring use (3+ emails across 2+ days). Until then they stay here — either we haven't observed any email yet, or we've seen a handful but not enough to call them a regular sender for the brand.

Microsoft 365 Proofpoint SparkPost

Probed: washingtonpost.com, bounces.washingtonpost.com, us-west-2.washingtonpost.com, email.washingtonpost.com, nl.mail.washingtonpost.com, comms.mail.washingtonpost.com, e.mail.washingtonpost.com

Where emails landed (Gmail)

Folder distribution across all emails from this brand observed in Gmail inboxes. High inbox % = good deliverability; spam appearances are the headline signal.

FolderCountShare
inbox 7 77.8%
promotions 2 22.2%

Where emails landed (Outlook)

Placement observed in Outlook / Microsoft 365 mailboxes. Focused Inbox splits mail into two tabs, "Focused" (inbox) and "Other", plus Junk. 11% reached the Focused inbox across 37 observed emails.

Focused 11% (4) Other 86% (32) Junk 3% (1)

Placement by ESP

Which ESP's emails are landing where. Sorted by spam % so problem senders surface first. Brands using one ESP for marketing and another for transactional often see very different placement profiles per ESP. Per-ESP folder data only started being captured recently — counts here may be smaller than the total above until backfill catches up.

ESP Emails Placement Inbox % Tabs % Spam %
Iterable 8
75.0% 25.0% 0.0%

ESP activity over time

May 5 – Jun 30, 2026 · 21 days with sends

Daily observations per ESP. Brands often run multiple ESPs concurrently — marketing on one, transactional on another — so this chart shows usage rather than switches.

6 0 Iterable: 1 (2026-05-05)1Iterable: 1 (2026-05-17)1Iterable: 1 (2026-05-25)1Iterable: 1 (2026-05-27)1Iterable: 1 (2026-06-01)1Iterable: 3 (2026-06-02)Amazon SES: 3 (2026-06-02)6Iterable: 5 (2026-06-03)Amazon SES: 1 (2026-06-03)6Iterable: 1 (2026-06-04)1Iterable: 2 (2026-06-05)Amazon SES: 1 (2026-06-05)3Iterable: 1 (2026-06-08)Amazon SES: 1 (2026-06-08)2Iterable: 1 (2026-06-09)Amazon SES: 1 (2026-06-09)2Amazon SES: 1 (2026-06-11)1Amazon SES: 1 (2026-06-12)1Iterable: 1 (2026-06-15)Amazon SES: 1 (2026-06-15)2Iterable: 3 (2026-06-16)3Iterable: 2 (2026-06-17)2Iterable: 2 (2026-06-18)2Iterable: 1 (2026-06-19)1Iterable: 4 (2026-06-22)4Iterable: 1 (2026-06-25)1Iterable: 2 (2026-06-30)205/0505/1105/1705/2305/2906/0406/1006/1606/2206/28
Iterable Amazon SES

Similar brands using Iterable

Sending IPs

IP addresses washingtonpost.com has been observed sending from, and where their mail landed in Gmail.

IPHostnameObsPlacementReputation
147.253.213.49 mta-253-213-49.sparkpostmail.com 8 1 Check →
147.253.210.35 mta-253-210-35.sparkpostmail.com 7 1 Check →
147.253.214.48 mta-253-214-48.sparkpostmail.com 7 Check →
156.70.24.202 mta-70-24-202.sparkpostmail.com 3 Check →
156.70.151.222 mta-70-151-222.sparkpostmail.com 2 Check →
147.253.211.72 unknown 2 Check →
54.240.58.245 unknown 2 Check →
54.240.35.250 unknown 2 Check →
54.240.59.46 unknown 2 Check →
54.240.33.91 unknown 1 Check →
54.240.58.236 unknown 1 Check →
54.240.59.125 unknown 1 Check →
54.240.59.143 unknown 1 Check →
54.240.36.48 unknown 1 Check →
54.240.36.1 unknown 1 Check →
54.240.33.80 unknown 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
nl.mail.washingtonpost.comIterable 27
washingtonpost.comAmazon SES 13
e.mail.washingtonpost.comIterable 8
comms.mail.washingtonpost.comIterable 2