Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Signin

signin.aws
🌐Web popularity #39,797 🏷 SaaS 🇺🇸United States

Signin uses Amazon SES as their primary email service provider. They're the #39,797 most-visited website overall, per Tranco (a web-popularity measure, not an email one). Email goes out from 2 different subdomains. Their email authentication setup is solid (score 85/100). Missing: one-click unsubscribe.

Transactional ESPAmazon SES
Total observations3
Active days2
Avg per active day1.5
Last activity📬 Active · 2 days ago
Cadence~every 3 days
Compare Signin 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
missing
SPF lookups 6/10

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

Authentication

DMARC reports sent to amazon.com. Policy p=reject means receivers actively block or quarantine spoofed mail.

SPF alignment: 67% of observed emails use an aligned return-path (mail.verify.signin.aws); the rest use third-party paths (amazonses.com) where DMARC has to rely on DKIM alignment.

DKIM alignment: all 3 observed emails sign with a domain aligned with signin.aws (verify.signin.aws, signin.aws). 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

Other SPF authorizations

No additional ESPs authorized in the brand's SPF beyond the confirmed senders above.

Probed: signin.aws, mail.verify.signin.aws, amazonses.com, verify.signin.aws

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 3 100.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 %
Amazon SES 3
100.0% 0.0% 0.0%

ESP activity over time

Jun 26 – Jun 30, 2026 · 2 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.

2 0 Amazon SES: 2 (2026-06-26)2Amazon SES: 1 (2026-06-30)106/2606/2706/2806/2906/30
Amazon SES

Similar brands using Amazon SES

Sending IPs

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

IPHostnameObsPlacementReputation
54.240.9.112 a9-112.smtp-out.amazonses.com 1 1 Check →
54.240.9.23 a9-23.smtp-out.amazonses.com 1 1 Check →
54.240.9.31 a9-31.smtp-out.amazonses.com 1 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
verify.signin.awsAmazon SES 2
signin.awsAmazon SES 1