| 24 | 20 | - Other parties with documented and verifiable lawful authority and purpose. |
| 25 | 21 | |
| 26 | 22 | ## How to Submit a Request |
| 27 | 23 | |
| 28 | 24 | Requests must be submitted via email to: |
| 29 | 25 | |
| 30 | | **RDRS@DreamHost.com** |
| 26 | **[\[email protected\]](https://dreamhost.com/cdn-cgi/l/email-protection)** |
| 31 | 27 | |
| 32 | | Your request must include the following: |
| 28 | Your request must include all of the following: |
| 33 | 29 | |
| 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 |
| 43 | 42 | |
| 44 | | > Requests that are incomplete, unsupported, or do not demonstrate necessity may be delayed or denied at DreamHost's sole discretion. |
| 43 | Requests that are incomplete, unsupported, or do not demonstrate necessity may be delayed or denied at DreamHost's sole discretion. |
| 45 | 44 | |
| 46 | 45 | ## Review and Disclosure Process |
| 47 | 46 | |
| 48 | 47 | Your 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. |
| 49 | 48 | |
| 50 | 49 | DreamHost 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. |