Parliament uses Mailchimp for marketing email and Amazon SES for transactional/notifications. They rank #8,514 in the Tranco list of most-popular domains. Email goes out from 2 different subdomains. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement.
Amazon SESAuthentication 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.
SPF / DKIM / DMARC above reflect the last 2 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to DMARC Analyzer (Mimecast). Policy
p=none is monitor-only — receivers won't act on spoofing yet.
SPF alignment: 33% of observed emails use an aligned return-path (mail.petition.parliament.uk); the rest use third-party paths (em9370.email.actionnetwork.org, mail97.use2001.mcdlv.net) where DMARC has to rely on DKIM alignment.
DKIM alignment: 56% of observed emails sign with an aligned DKIM key (petition.parliament.uk, parliament.uk); the rest sign with third-party keys (email.actionnetwork.org) where DMARC has to rely on SPF alignment.
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
None — only the primary ESP(s) shown aboveESPs 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.
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.
Probed: parliament.uk, mail.petition.parliament.uk, em9370.email.actionnetwork.org, mail97.use2001.mcdlv.net, petition.parliament.uk
Folder distribution across all emails from this brand observed in Gmail inboxes. High inbox % = good deliverability; spam appearances are the headline signal.
| Folder | Count | Share |
|---|---|---|
| inbox | 7 | 87.5% |
| promotions | 1 | 12.5% |
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 % |
|---|---|---|---|---|---|
| Mailchimp | 2 | 50.0% | 50.0% | 0.0% | |
| Amazon SES | 4 | 100.0% | 0.0% | 0.0% |
Daily observations per ESP. Brands often run multiple ESPs concurrently — marketing on one, transactional on another — so this chart shows usage rather than switches.
IP addresses parliament.uk has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 148.105.0.97 | mail97.use2001.mcdlv.net |
2 | — | Check → |
| 54.240.6.12 | a6-12.smtp-out.eu-west-1.amazonses.com |
2 | — | Check → |
| 148.105.15.73 | mail73.sea91.rsgsv.net |
1 | — | Check → |
| 167.89.57.84 | o9.mailings.actionnetwork.org |
1 | — | Check → |
| 54.240.50.192 | a50-192.smtp-out.eu-west-1.amazonses.com |
1 | — | Check → |
| 54.240.6.151 | a6-151.smtp-out.eu-west-1.amazonses.com |
1 | 1 | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
petition.parliament.uk | Amazon SES 4 | |
parliament.uk | Mailchimp 3 |