Tracked subprocessors 0 Subprocessor of 3 Third parties loaded 5 Loaded by 0
+ − ⟲
No tracked subprocessors.
Not loaded by any published homepage.
Subprocessors None extracted.
Name.com's homepage made 846 requests to 10 domains, 5 services controlled by another company, and 1 domain not identified.
Advertising (1): Google Cloud Analytics (1): Cloudflare Cookie compliance (1): usually detected as Cookie compliance: OneTrust Other (2): Affiliate programs: Impact Radius; usually detected as CMS: Sanity 5 third parties by category: Advertising 1 Analytics 1 Cookie compliance 1 Other 2
Third parties 5 · 25 requests
Google Cloud DoubleClick Floodlight Google Analytics Google Tag Manager 2% of the page's requests 18 Sanity sanity.io <1% of the page's requests 3 Cloudflare Cloudflare Browser Insights <1% of the page's requests 1 OneTrust onetrust.com <1% of the page's requests 1 Unknown 1 · 1 request
ojrq.net
First party 1 · 820 requests
Name.com Cloudflare HTTP/3 Nuxt UI Nuxt.js OneTrust Open Graph PWA PostHog Priority Hints Sanity Sanity.io Vue.js Zendesk Widget 97% of the page's requests 820
5 tracked companies loaded by the homepage are not in Name.com's subprocessor list. A website can use a service without it processing customer data.
Aug 15: no incident reported Aug 16: no incident reported Aug 17: no incident reported Aug 18: no incident reported Aug 19: no incident reported Aug 20: no incident reported Aug 21: no incident reported Aug 22: no incident reported Aug 23: no incident reported Aug 24: no incident reported Aug 25: no incident reported Aug 26: no incident reported Aug 27: no incident reported Aug 28: no incident reported Aug 29: no incident reported Aug 30: no incident reported Aug 31: no incident reported Sep 1: no incident reported Sep 2: no incident reported Sep 3: no incident reported Sep 4: no incident reported Sep 5: no incident reported Sep 6: no incident reported Sep 7: no incident reported Sep 8: no incident reported Sep 9: no incident reported Sep 10: no incident reported Sep 11: no incident reported Sep 12: no incident reported Sep 13: no incident reported Sep 14: no incident reported Sep 15: no incident reported Sep 16: no incident reported Sep 17: no incident reported Sep 18: no incident reported Sep 19: no incident reported Sep 20: no incident reported Sep 21: no incident reported Sep 22: no incident reported Sep 23: no incident reported Sep 24: no incident reported Sep 25: no incident reported Sep 26: no incident reported Sep 27: no incident reported Sep 28: no incident reported Sep 29: no incident reported Sep 30: no incident reported Oct 1: 1 incident (1 no impact stated) Oct 2: no incident reported Oct 3: no incident reported Oct 4: no incident reported Oct 5: no incident reported Oct 6: no incident reported Oct 7: no incident reported Oct 8: no incident reported Oct 9: no incident reported Oct 10: no incident reported Oct 11: no incident reported Oct 12: no incident reported Oct 13: no incident reported Oct 14: no incident reported Oct 15: no incident reported Oct 16: no incident reported Oct 17: no incident reported Oct 18: no incident reported Oct 19: no incident reported Oct 20: no incident reported Oct 21: no incident reported Oct 22: no incident reported Oct 23: no incident reported Oct 24: no incident reported Oct 25: no incident reported Oct 26: no incident reported Oct 27: no incident reported Oct 28: no incident reported Oct 29: no incident reported Oct 30: no incident reported Oct 31: no incident reported Nov 1: no incident reported Nov 2: no incident reported Nov 3: 1 incident (1 no impact stated) Nov 4: no incident reported Nov 5: no incident reported Nov 6: no incident reported Nov 7: no incident reported Nov 8: no incident reported Nov 9: no incident reported Nov 10: no incident reported Nov 11: no incident reported Nov 12: no incident reported 90 days ago today
2 incidents in 90 days0 major or critical33 days typical time to resolveIncidents per month 0 2 4 Dec 2025: 0 incidents Jan 2026: 0 incidents Feb 2026: 0 incidents Mar 2026: 0 incidents Apr 2026: 1 incident (1 critical) · typical time to resolve 1 h 29 min May 2026: 1 incident (1 major) · typical time to resolve 2 h 6 min Jun 2026: 0 incidents Jul 2026: 2 incidents (1 minor, 1 no impact stated) · typical time to resolve 5 min Aug 2026: 0 incidents Sep 2026: 0 incidents Oct 2026: 1 incident (1 no impact stated) · typical time to resolve 33 days Nov 2026: 1 incident (1 no impact stated) Dec 2025 Jan 2026 Feb Mar Apr May Jun Jul Aug Sep Oct Nov critical major minor no impact stated
Components affected Component Incidents Bar name.com Registry Connections 1
As Name.com's status page reports its own incidents (scheduled maintenance left out), read every few hours since Nov 1, 2025 (evidence )
None since tracking began.