Requesting Access to Nonpublic Domain Registration Data

FIRST SEEN 2026-07-29 · VERSION 20260729_rev01 · COMPARED WITH 20250724_rev01

Full text changes — 20250724_rev01 to 20260729_rev01

COLOUR MARKS THE SEVERITY OF A FLAGGED CLAUSE · + AND − MARK ADDED AND REMOVED

1#### Last Updated:
2
3July 10, 2025
4
51## Requesting Access to Nonpublic Domain Registration Data
62
73DreamHost is committed to balancing privacy obligations with lawful access. We process requests for nonpublic domain registration data in accordance with ICANN's Registration Data Policy (RDP) and applicable data protection laws. Access to redacted registration data is restricted to protect registrant privacy, but may be granted in limited circumstances where a legitimate interest and legal basis are demonstrated.
84
95## Before You Request Access
106
2420- Other parties with documented and verifiable lawful authority and purpose.
2521
2622## How to Submit a Request
2723
2824Requests must be submitted via email to:
2925
30**RDRS@DreamHost.com**
26**[\[email protected\]](https://dreamhost.com/cdn-cgi/l/email-protection)**
3127
32Your request must include the following:
28Your request must include all of the following:
3329
34- **Full legal name and organization** (if applicable)
35- **Contact details** (email address, phone number, and postal address)
36- **Domain name(s)** associated with the request
37- **Specific data requested** (e.g., registrant name or email address)
38- **Purpose and legal basis** (e.g., GDPR Article 6(1)(f), regulatory inquiry, pending litigation, etc)
39- **Nature of the request** (e.g., the domain name is infringing third party rights, contents or services offered infringe third party rights or statutory law, DNS security issues, etc.)
40- **Summary of prior contact attempts** and outcomes
41- **Data handling and retention policies** consistent with applicable privacy laws
42- **Supporting documentation** (e.g., legal filings, UDRP complaint number, abuse report reference)
30- Full legal name and organization (if applicable)
31- Contact details (email address, phone number, and postal address)
32- Domain name(s) associated with the request
33- Specific data requested (e.g., registrant name or email address)
34- Purpose and legal basis (e.g., regulatory inquiry, pending litigation)
35- Authority to submit the request (e.g., acting on your own behalf, or confirmation you are authorized to act for the relevant party)
36- Nature of the request (e.g., the domain name is infringing third party rights, contents or services offered infringe third party rights or statutory law, or DNS security issues)
37- Case summary sufficient to evaluate the request, including, as applicable: relevant statute/law and applicability, competent jurisdiction/court, and why the requested data is necessary to pursue further action
38- Summary of prior contact attempts and outcomes
39- Data handling and retention policies consistent with applicable privacy laws, including confirmation that any personal data disclosed will be processed, stored, and transferred in compliance with applicable data protection laws and not shared unlawfully
40- Supporting documentation (e.g., legal filings, UDRP complaint number, abuse report reference)
41- Accuracy and completeness attestation confirming the submission is complete and accurate to the best of your knowledge, and acknowledging responsibility under applicable law for requests made under false pretenses
4342
44> Requests that are incomplete, unsupported, or do not demonstrate necessity may be delayed or denied at DreamHost's sole discretion.
43Requests that are incomplete, unsupported, or do not demonstrate necessity may be delayed or denied at DreamHost's sole discretion.
4544
4645## Review and Disclosure Process
4746
4847Your request will be reviewed by our Compliance Team to assess legal sufficiency and necessity. If additional information is required, we will contact you for clarification.
4948
5049DreamHost will only consider requests that involve currently registered, complete, and specifically identified domain names. We do not provide historical or archival registration data, partial or wildcard domain name matches, or data based on domain name searches or patterns.