Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Theverge

theverge.com
🏆Rank #780 🏷 Media 🇺🇸United States 📥 Inbox 62%

Theverge uses Sailthru as their primary email service provider. They rank #780 in the Tranco list of most-popular domains. Their email authentication setup is solid (score 85/100).

Marketing ESPSailthru
Total observations80
Active days32
Avg per active day2.5
Last activity📬 Active · yesterday
Cadence~every 2 days

Other technologies

Non-ESP tools detected in this brand's emails. Independent of who sends — a brand can use any combination.

HTML builder Beefree SDK
Compare Theverge with another brand:

Email setup 85/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.
85/100
SPF
pass
DKIM
pass
DMARC
pass (reject)
BIMI
none
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 dmarcian. Policy p=reject means receivers actively block or quarantine spoofed mail.

SPF alignment: all 76 observed emails use a return-path aligned with theverge.com (bouncest.theverge.com). SPF authenticates the visible From — supports DMARC directly.

DKIM alignment: all 50 observed emails sign with a domain aligned with theverge.com (theverge.com). DKIM authenticates the visible From — supports DMARC directly.

Transport & deliverability

TLS: modern — 100% TLS 1.3 (across 29 sends).

Delivery: fast — 85% of emails in the last 7 days arrive in under 10 seconds (across 13 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.

Sailthru ✓ confirmed

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.

Amazon SES Google Workspace

Probed: theverge.com, bouncest.theverge.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 44 62.0%
promotions 27 38.0%

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 %
Sailthru 67
65.7% 34.3% 0.0%

ESP activity over time

May 1 – Jun 29, 2026 · 36 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.

7 0 Sailthru: 1 (2026-05-01)1Sailthru: 2 (2026-05-05)2Sailthru: 1 (2026-05-06)1Sailthru: 1 (2026-05-08)1Sailthru: 1 (2026-05-11)1Sailthru: 3 (2026-05-12)3Sailthru: 2 (2026-05-14)2Sailthru: 1 (2026-05-15)1Sailthru: 7 (2026-05-16)7Sailthru: 6 (2026-05-18)6Sailthru: 6 (2026-05-19)6Sailthru: 1 (2026-05-21)1Sailthru: 1 (2026-05-25)1Sailthru: 2 (2026-05-27)2Sailthru: 2 (2026-05-28)2Sailthru: 2 (2026-06-01)2Sailthru: 1 (2026-06-02)1Sailthru: 3 (2026-06-03)3Sailthru: 2 (2026-06-04)2Sailthru: 6 (2026-06-08)6Sailthru: 1 (2026-06-09)1Sailthru: 1 (2026-06-10)1Sailthru: 1 (2026-06-11)1Sailthru: 2 (2026-06-12)2Sailthru: 1 (2026-06-13)1Sailthru: 1 (2026-06-15)1Sailthru: 2 (2026-06-16)2Sailthru: 2 (2026-06-17)2Sailthru: 2 (2026-06-18)2Sailthru: 3 (2026-06-22)3Sailthru: 2 (2026-06-23)2Sailthru: 2 (2026-06-24)2Sailthru: 2 (2026-06-25)2Sailthru: 3 (2026-06-26)3Sailthru: 3 (2026-06-27)3Sailthru: 1 (2026-06-29)105/0105/0705/1305/1905/2505/3106/0606/1206/1806/2406/29
Sailthru

Similar brands using Sailthru

Sending IPs

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

IPHostnameObsPlacementReputation
192.64.236.55 mta236-55.sailthru.com 2 Check →
192.64.236.58 nj15mta-58.sailthru.com 2 Check →
192.64.237.76 mta237-76.sailthru.com 1 Check →
192.64.236.215 mta236-215.sailthru.com 1 Check →
192.64.237.111 mta237-111.sailthru.com 1 Check →
192.64.236.72 pmta236-72.sailthru.com 1 Check →
192.64.236.162 mta236-162.sailthru.com 1 Check →
192.64.236.219 mta236-219.sailthru.com 1 Check →
192.64.236.30 mta236-30.sailthru.com 1 Check →
192.64.237.47 mta237-47.sailthru.com 1 Check →
192.64.236.152 nj11mta-152.sailthru.com 1 Check →
192.64.236.80 mta236-80.sailthru.com 1 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
theverge.comSailthru 80