SendGrid (inbound routing) mailbox provider
According to Live Direct Marketing's daily Tranco top-1M scan (September 16, 2026), SendGrid (inbound routing) is the mailbox provider for 206 domains — 0.03% of 672,143 domains with MX records. Detection method: primary MX record (lowest preference).
Key facts
- 206 domains in the Tranco top-1M use SendGrid (inbound routing) (0.03% of domains with MX records).
- Snapshot date: 2026-09-16 — recomputed every day.
- Strongest TLD: .com (44.7% of its domains).
- Region skew: Global / US-skewed.
- Most co-used service: SendGrid (Twilio).
- Directory category: email service provider.
Why SendGrid (inbound routing) appears in this category
Twilio SendGrid inbound parse.
We classify it as a email service provider from primary MX record (lowest preference) matching a maintained provider rule. This is infrastructure attribution from public DNS, not evidence of a direct contract or exclusive use.
SendGrid Inbound Parse is an email routing service operated by Twilio that accepts inbound mail on behalf of a website. When a domain lists SendGrid's servers as its primary MX record, all incoming messages are received by Twilio's infrastructure, parsed into structured data, and forwarded to a webhook URL or email address configured by the domain owner. This architecture allows organisations to process email programmatically without running their own mail servers.
The presence of SendGrid's MX records indicates that the recipient organisation is handling inbound mail through Twilio's cloud infrastructure rather than traditional on-premises mail stacks. For senders, this means deliverability behaviour, bounce processing, and rejection logic are mediated by SendGrid's systems. The footprint of SendGrid inbound routing concentrates in smaller and mid-market domains—particularly in the .com space—suggesting it appeals to organisations building lightweight, API-driven mail workflows rather than enterprise-scale mail operations.
Where SendGrid (inbound routing) sits in the Tranco ranking
| Tranco rank band | Domains | Share of its base |
|---|---|---|
| Top 1,000 | 1 | 0.5% |
| Top 10,000 | 2 | 1.0% |
| Top 100,000 | 27 | 13.1% |
| Top 1,000,000 | 172 | 83.5% |
| Unranked | 4 | 1.9% |
Top-level domain split
| TLD | Domains | Share | |
|---|---|---|---|
| .com | 92 | 44.7% | |
| .jp | 19 | 9.2% | |
| .net | 16 | 7.8% | |
| .org | 7 | 3.4% | |
| .app | 6 | 2.9% | |
| .co | 5 | 2.4% | |
| .io | 5 | 2.4% | |
| .com.br | 5 | 2.4% | |
| .jobs | 4 | 1.9% | |
| .com.au | 3 | 1.5% |
What SendGrid (inbound routing) users also use
Cross-tabulated from the same daily snapshot — the other email services seen on the same 206 domains.
| Type | Service | Domains | Share of SendGrid (inbound routing) users |
|---|---|---|---|
| ESP | SendGrid (Twilio) | 75 | 36.4% |
| ESP | Mailgun | 9 | 4.4% |
| ESP | Amazon SES | 8 | 3.9% |
| ESP | Zendesk | 3 | 1.5% |
| ESP | Mandrill | 2 | 1.0% |
| ESP | BizMatrix | 2 | 1.0% |
| ESP | Campaign Monitor | 1 | 0.5% |
| ESP | Namecheap Forwarding | 1 | 0.5% |
| ESP | Proofpoint | 1 | 0.5% |
| ESP | Microsoft 365 US Gov | 1 | 0.5% |
Bounce and rejection handling via SendGrid's parsing layer
When a message is rejected or bounces at a domain using SendGrid's inbound routing, the bounce notification is generated and processed by SendGrid's systems according to the Inbound Parse webhook configuration. SendGrid applies its own message filters before the webhook handler receives it; email with malformed headers, unusual character encoding, or non-standard structure may be silently dropped, deferred, or rejected before the recipient's application ever processes it. Senders targeting such addresses should understand that their message structure must satisfy both SendGrid's parsing requirements and the recipient's webhook logic, introducing an additional filtering layer beyond what would occur with direct SMTP delivery to a traditional mail server.
See the full SendGrid (inbound routing) data page (KPI cards, trend, sample domains) →
Run a free inbox-placement test across Gmail, Outlook, Yahoo and more — see exactly where your mail lands and why.
Frequently asked questions
Should I test email deliverability against domains using SendGrid inbound routing?
Yes, if your recipient domain uses SendGrid's MX records, testing how SendGrid's Inbound Parse handles your message structure is essential for reliable delivery, since the service applies its own parsing filters. However, testing a live endpoint requires permission from the domain owner; use a sandbox environment or an endpoint under your control.
How many domains use SendGrid (inbound routing)?
206 domains in the Tranco top-1M use SendGrid (inbound routing) as their mailbox provider as of September 16, 2026 (0.03% of domains with MX records), according to Live Direct Marketing's daily DNS scan.
Is SendGrid (inbound routing) common enough to affect email deliverability testing?
SendGrid (inbound routing) accounts for 0.03% of domains with MX records in the top 1M. Whether you should seed a test mailbox there depends on how much of your audience it represents — the co-usage table above shows the services it appears alongside most.
Which countries or TLDs use SendGrid (inbound routing) most?
SendGrid (inbound routing)'s largest TLD is .com (44.7% of its domains); it appears across 46 TLDs in total.