Capgemini uses Amazon SES as their primary email service provider. They rank #5,768 in the Tranco list of most-popular domains. We've also observed sends via SendGrid. Email goes out from 2 different subdomains. Their email authentication setup is solid (score 85/100). Missing: one-click unsubscribe.
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.
DMARC reports sent to capgemini.com. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: all 7 observed emails use a return-path aligned with capgemini.com (mail.jobs.capgemini.com, imochasgmails.capgemini.com). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 4 observed emails sign with a domain aligned with capgemini.com (jobs.capgemini.com, capgemini.com). DKIM authenticates the visible From — supports DMARC directly.
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
SendGrid 1ESPs 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: capgemini.com, mail.jobs.capgemini.com, imochasgmails.capgemini.com, jobs.capgemini.com
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 | 100.0% |
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 % |
|---|---|---|---|---|---|
| SendGrid | 1 | 100.0% | 0.0% | 0.0% | |
| Amazon SES | 6 | 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 capgemini.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Reputation |
|---|---|---|---|
| 54.240.115.219 | a115-219.smtp-out.us-east-2.amazonses.com |
6 | Check → |
| 159.183.184.112 | o2.ptr4351.imocha.io |
1 | Check → |
Per-IP inbox / promotions / spam is being collected and will appear here as new emails are observed.
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
jobs.capgemini.com | Amazon SES 6 | |
capgemini.com | SendGrid 1 |
