Incident uses HubSpot for marketing email and SendGrid for transactional/notifications. They rank #47,870 in the Tranco list of most-popular domains. We've also observed sends via 2 other providers: Brevo, Kit. Email goes out from 2 different subdomains. Their email authentication setup is good (score 80/100). We've recorded 2 ESP changes since first observing this brand.
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 10 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to DMARC Digests. Policy
p=quarantine means receivers actively block or quarantine spoofed mail.
SPF alignment: 87% of observed emails use an aligned return-path (em1464.status.incident.io, em9094.incident.io); the rest use third-party paths (bf05.eu1.hubspotemail.net) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 49 observed emails sign with a domain aligned with incident.io (status.incident.io, incident.io). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 88% TLS 1.3 (across 26 sends).
Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 11 sends).
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
Brevo 3 Kit 2ESPs 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: incident.io, bf05.eu1.hubspotemail.net, em9094.incident.io, em1464.status.incident.io, status.incident.io, ptr1198.incident.io, ptr701.incident.io
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 | 52 | 98.1% |
| promotions | 1 | 1.9% |
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 % |
|---|---|---|---|---|---|
| HubSpot | 4 | 75.0% | 25.0% | 0.0% | |
| Kit | 2 | 100.0% | 0.0% | 0.0% | |
| SendGrid | 34 | 100.0% | 0.0% | 0.0% | |
| Brevo | 3 | 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 incident.io has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 159.183.12.67 | o2.ptr1198.incident.io |
53 | 12 | Check → |
| 143.244.83.22 | bd77ezs.bf05.eu1.hubspotemail.net |
3 | — | Check → |
| 143.244.81.20 | bd77eli.bf05.eu1.hubspotemail.net |
3 | 1 | Check → |
| 159.183.103.201 | o1.ptr701.incident.io |
2 | — | Check → |
| 143.244.83.20 | bd77ezq.bf05.eu1.hubspotemail.net |
1 | — | Check → |