GitLab uses Marketo for marketing email and Mailgun for transactional/notifications. They rank #414 in the Tranco list of most-popular domains. We've also observed sends via Iterable. Email goes out from 3 different subdomains. Their email authentication setup is solid (score 85/100).
Non-ESP tools detected in this brand's emails. Independent of who sends — a brand can use any combination.
| HTML builder |
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.
SPF / DKIM / DMARC above reflect the last 3 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to vali.email. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: observed emails use a third-party return-path (potomac1050.mktomail.com) — SPF passes there but doesn't align with gitlab.com, so DMARC has to rely on DKIM alignment.
DKIM alignment: all 9 observed emails sign with a domain aligned with gitlab.com (mg.gitlab.com, gitlab.com, mail.gitlab.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: 0% TLS 1.3, 100% TLS 1.2 (across 5 sends).
Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 3 sends).
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
Iterable 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: gitlab.com, potomac1050.mktomail.com, mg.gitlab.com, mail.gitlab.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 | 10 | 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 % |
|---|---|---|---|---|---|
| Marketo | 2 | 100.0% | 0.0% | 0.0% | |
| Iterable | 1 | 100.0% | 0.0% | 0.0% | |
| Mailgun | 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 gitlab.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 159.112.247.232 | v5232.v5478dbc4.use4.send.mailgun.net |
3 | 2 | Check → |
| 159.112.247.23 | v523.v5478dbc4.use4.send.mailgun.net |
2 | 1 | Check → |
| 199.15.213.50 | potomac1050.mktomail.com |
2 | — | Check → |
| 192.28.150.227 | potomac1227.mktomail.com |
1 | — | Check → |
| 159.112.247.228 | v5228.v5478dbc4.use4.send.mailgun.net |
1 | — | Check → |
| 159.112.240.144 | v5144.v5fc25cd0.use4.send.mailgun.net |
1 | — | Check → |
