Contact Information
Language note
The English version of Hostwover's legal agreements and policies is the authoritative version. Translated versions are provided for convenience. If there is any conflict between translations, the English version shall prevail.
Last updated: August 15, 2026
This Contact Information page explains how Customers, visitors, rights holders, security researchers, authorities, and other persons may contact Hostwover for support, billing, domain, privacy, security, abuse, intellectual property, legal, and other Service-related matters.
To help Hostwover route and process requests efficiently, please use the appropriate contact category described below.
1. Hostwover
Brand / Trading Name: Hostwover
Website:
hostwover.com
Country of Operation / Establishment:
Egypt
Hostwover provides online infrastructure and digital services including domain services, Web Hosting, VPS, VDS, Professional Email, Google Workspace, and other technology Services.
2. General Contact
For general questions concerning Hostwover or Hostwover Services:
Hostwover Support
Email: [email protected]
Website: hostwover.com
This is currently Hostwover's primary public contact channel.
3. Customer Support
For Customer-support matters, contact:
Customer Support may assist with matters including:
- account questions.
- Service configuration.
- provisioning.
- technical issues.
- access problems.
- domains.
- hosting.
- VPS.
- VDS.
- Professional Email.
- Google Workspace.
- renewals.
- billing; and
- other Hostwover Services.
4. Authenticated Support
Where an authenticated Hostwover support portal or account dashboard is available, Customers should preferably use that interface for account-specific matters.
Authenticated support helps Hostwover verify that the requester is authorized to manage the relevant account or Service.
5. Support Availability
Support requests may generally be submitted electronically at any time through available Hostwover support channels.
Submission availability does not guarantee:
- an immediate human response.
- immediate resolution.
- continuous staffing of every support channel; or
- a particular response time.
Support handling is governed by the Hostwover Customer Service Policy.
6. General Support Subject
When contacting Hostwover by email, use a descriptive subject.
For example:
Support Request – [Service / Domain]
or:
Account Support – [Issue]
7. Account Information
Where appropriate, include:
- Customer name.
- Hostwover account email.
- relevant domain.
- Service.
- order number.
- invoice number.
- server identifier.
- subscription identifier; or
- existing support ticket number.
Do not provide information unrelated to the request.
BILLING
8. Billing Contact
For:
- invoices.
- payments.
- failed payments.
- duplicate payments.
- billing cycles.
- renewal charges.
- account balances.
- billing errors; or
- other payment questions,
contact:
Suggested subject:
Billing Request – [Invoice / Order Number]
9. Refund Requests
Refund requests should currently be submitted to:
Suggested subject:
Refund Request – [Order / Invoice Number]
Refund eligibility is governed by the Hostwover Refund Policy and applicable product agreement.
10. Information for Refund Requests
Where applicable, include:
- Customer account.
- order number.
- invoice number.
- affected Service.
- transaction date.
- amount.
- reason for the request; and
- relevant supporting information.
11. Payment Disputes
If you believe a Hostwover charge is incorrect, contact Hostwover as soon as reasonably possible.
Suggested subject:
Billing Dispute – [Transaction / Invoice]
Where practical, contacting Hostwover before initiating a chargeback may allow the matter to be investigated directly.
12. Payment Security
Do not send through ordinary email:
- full payment-card numbers.
- card security codes.
- online banking passwords.
- payment authentication codes; or
- other unnecessary financial credentials.
DOMAIN SERVICES
13. Domain Support
For questions involving:
- domain registration.
- domain availability.
- transfer.
- renewal.
- expiration.
- redemption.
- restoration.
- nameservers.
- DNS.
- domain status; or
- domain verification,
contact:
Suggested subject:
Domain Support – example.com
14. Domain Registration Issues
When reporting a domain-registration issue, include:
- domain name.
- order number where available.
- Hostwover account.
- date of attempted registration; and
- description of the problem.
15. Domain Transfer Issues
For transfer assistance, use:
Suggested subject:
Domain Transfer – example.com
Do not include the domain's Auth/EPP code in an ordinary initial email unless Hostwover specifically instructs you to provide it through an appropriate secure process.
16. Domain Expiration and Recovery
If a domain has already expired, contact Hostwover as soon as possible.
Suggested subject:
URGENT – Expired Domain – example.com
Recovery options may decrease as a domain progresses through its expiration lifecycle.
17. Domain Disputes
For disputes involving:
- domain ownership.
- registrant control.
- unauthorized transfer.
- trademark claims.
- UDRP.
- URS.
- court proceedings; or
- competing ownership claims,
contact:
Suggested subject:
Domain Dispute – example.com
The Hostwover Domain Dispute Policy applies.
18. Domain Abuse Is Different
A domain ownership or trademark dispute is different from an abuse report.
Reports involving:
- phishing.
- malware.
- botnets.
- fraud.
- DNS abuse; or
- malicious activity
should follow the Abuse Reporting section below.
WEB HOSTING
19. Web Hosting Support
For Web Hosting assistance, contact:
Suggested subject:
Web Hosting Support – [Domain]
Include information such as:
- affected domain.
- hosting account.
- error message.
- approximate time of the problem; and
- relevant troubleshooting information.
20. Website Development Requests
Ordinary hosting support does not automatically include custom website development or application debugging.
Where Hostwover offers such services separately, the applicable commercial arrangement will control.
VPS
21. VPS Support
For VPS matters, contact:
Suggested subject:
VPS Support – [Server Identifier / Hostname]
Useful information may include:
- server identifier.
- hostname.
- affected IP address.
- operating system.
- approximate incident time.
- error message; and
- description of the problem.
22. VPS Security Incidents
If you believe your VPS has been compromised, use a clear subject such as:
URGENT – VPS Security Incident – [Server Identifier]
Do not send:
- root passwords.
- SSH private keys.
- database passwords; or
- API secrets
through ordinary email.
VDS
23. VDS Support
24. VDS Security
Suspected VDS compromises should be reported promptly.
Suggested subject:
URGENT – VDS Security Incident – [Server Identifier]
PROFESSIONAL EMAIL
25. Professional Email Support
For Professional Email assistance:
Suggested subject:
Professional Email Support – [Domain]
Hostwover may assist with:
- provisioning.
- mailbox status.
- storage.
- DNS.
- MX records.
- SPF.
- DKIM.
- supported mail settings; and
- Service-related issues.
26. Compromised Mailboxes
If you believe a mailbox has been compromised, contact Hostwover promptly.
Suggested subject:
URGENT – Compromised Mailbox – [Email Address]
Do not send the mailbox password in the email.
GOOGLE WORKSPACE
27. Google Workspace Support
For Google Workspace purchased through Hostwover:
Suggested subject:
Google Workspace Support – [Domain]
28. Workspace Information
Include where relevant:
- Customer domain.
- subscription.
- affected user.
- license issue.
- domain-verification issue; and
- description of the problem.
Do not send Google account passwords.
PRIVACY AND DATA PROTECTION
29. Privacy Contact
Until Hostwover officially publishes a dedicated privacy contact, privacy and Personal Data requests may be submitted to:
Suggested subject:
Privacy Request – [Type of Request]
30. Privacy Request Types
Privacy requests may concern:
- access.
- correction.
- deletion.
- restriction.
- objection.
- consent withdrawal.
- Personal Data concerns.
- privacy complaints; or
- other applicable data-protection rights.
Applicable rights depend on the relevant law.
31. Privacy Request Information
A privacy request should provide enough information for Hostwover to:
- identify the requester.
- understand the request.
- locate the relevant Personal Data; and
- determine the applicable account or Service.
32. Privacy Verification
Hostwover may require reasonable identity or account verification before:
- disclosing Personal Data.
- deleting Personal Data.
- changing Personal Data; or
- processing another sensitive privacy request.
33. Dedicated Privacy Contact
Hostwover may establish an address such as:
If and when such an address is officially created, monitored, and published, Hostwover may direct privacy requests to that channel.
Until then, use:
34. Data Protection Officer
If Hostwover becomes legally required to publish contact details for a formally appointed or registered Data Protection Officer, those details will be added to this page.
Hostwover should not publish a fictitious or unverified DPO contact.
ABUSE
35. Abuse Reports
Suspected abuse involving Hostwover Services may currently be reported to:
Suggested subject:
Abuse Report – [Domain / IP / Service]
36. Abuse Examples
Abuse reports may involve:
- phishing.
- malware.
- ransomware.
- spam.
- botnets.
- DDoS attacks.
- network attacks.
- fraud.
- compromised servers.
- malicious domains.
- DNS abuse.
- unlawful content; or
- other violations of Hostwover policies.
37. Abuse Report Information
Where available, include:
- affected domain.
- URL.
- IP address.
- hostname.
- description.
- timestamps.
- timezone.
- screenshots.
- logs.
- email headers; and
- other relevant evidence.
38. Full URLs
For website abuse, please provide the full URL where possible rather than only the domain name.
This can help Hostwover identify the specific affected resource.
39. Spam Complaints
Spam complaints should preferably include:
- complete email headers.
- sending address.
- receiving address.
- sending IP.
- message timestamp; and
- message content relevant to the complaint.
40. Malware Reports
Malware reports should include where possible:
- affected URL.
- domain.
- file hash.
- malware detection information.
- timestamp; and
- technical evidence.
41. Future Abuse Contact
Hostwover may establish a dedicated address such as:
Do not rely on that address until Hostwover officially confirms that it exists and is actively monitored.
Current contact:
SECURITY VULNERABILITIES
42. Security Vulnerability Reports
Security researchers who discover a vulnerability affecting a Hostwover-controlled system should currently report it to:
Suggested subject:
Security Vulnerability Report – [Short Description]
43. Urgent Security Vulnerabilities
For vulnerabilities creating an immediate serious risk, use:
URGENT SECURITY VULNERABILITY – [Short Description]
44. Responsible Disclosure Policy
Security research is governed by the:
Hostwover Responsible Disclosure Policy
Researchers should review that Policy before conducting security testing.
45. Customer Systems Are Not Included
Hostwover's Responsible Disclosure process does not authorize testing of:
- Customer websites.
- Customer VPS instances.
- Customer VDS instances.
- Customer applications.
- Customer mailboxes; or
- third-party provider infrastructure.
46. Security Report Content
A useful security report should include:
- affected Hostwover asset.
- vulnerability type.
- reproduction steps.
- security impact.
- proof of concept where appropriate.
- researcher contact information; and
- any disclosure considerations.
47. Sensitive Vulnerability Evidence
Do not send unnecessary:
- database dumps.
- Customer Personal Data.
- passwords.
- complete access tokens.
- private keys.
- payment-card information; or
- unrelated confidential information.
48. Future Security Contact
Hostwover may establish:
Once officially published as an active security contact, it may replace the general support channel for vulnerability reports.
COPYRIGHT
49. Copyright Complaints
Copyright complaints may currently be sent to:
Suggested subject:
Copyright Complaint – [Domain / URL]
50. Copyright Complaint Information
Include where applicable:
- copyright owner.
- authorized representative.
- copyrighted work.
- allegedly infringing material.
- exact URL.
- explanation of the complaint.
- contact information.
- required good-faith statements; and
- signature where applicable.
The Hostwover Trademark & Copyright Policy applies.
51. DMCA Notices
The general Hostwover support address should not be assumed to be a registered U.S. DMCA Designated Agent unless Hostwover expressly publishes verified designated-agent information.
Where a formal statutory process applies, the applicable legal requirements must be followed.
TRADEMARKS
52. Trademark Complaints
Trademark complaints may currently be sent to:
Suggested subject:
Trademark Complaint – [Domain / URL]
53. Trademark Complaint Information
Provide where applicable:
- trademark owner.
- trademark.
- registration number.
- jurisdiction.
- goods or services.
- complained-of content.
- exact URLs.
- explanation.
- requested action; and
- evidence of authorization.
54. Trademark Domain Disputes
If the requested remedy is transfer or cancellation of a domain, the matter may need to proceed under the:
Hostwover Domain Dispute Policy
and applicable:
- UDRP.
- URS.
- ccTLD procedure.
- registrar procedure.
- court process; or
- other recognized dispute mechanism.
LEGAL COMMUNICATIONS
55. General Legal Communications
Until Hostwover officially publishes a dedicated legal contact, general legal communications may be sent to:
Suggested subject:
Legal Communication – [Matter]
56. Legal Contact Does Not Mean Formal Service
Sending legal documents to Customer Support does not necessarily constitute valid formal service of legal process.
Where applicable law requires a particular form or location of service, that procedure must be followed.
57. Formal Legal Service
Hostwover's formal legal-service details should be published only after the relevant:
- legal entity name.
- business address.
- authorized recipient.
- legal email; and
- service procedure
have been verified.
58. Future Legal Contact
Hostwover may establish:
as a dedicated legal contact.
Until it is officially confirmed and monitored, use:
for general communications.
59. Court Orders
Persons submitting a court order or other official legal process should include:
- issuing authority.
- case number.
- affected account, domain, or Service.
- requested action.
- official contact details; and
- complete legal documentation.
Hostwover may verify authenticity before acting.
60. Law-Enforcement Requests
Law-enforcement or government requests should clearly identify:
- requesting authority.
- official representative.
- official contact information.
- applicable legal authority.
- requested information.
- relevant account/domain identifiers; and
- applicable deadline.
Hostwover may require verification through an independent official channel.
61. Emergency Legal Requests
Where a legally authorized authority has an emergency involving an imminent risk of serious harm, the request should clearly identify:
EMERGENCY LEGAL REQUEST
in the subject.
Submission of an emergency label does not itself establish legal validity or authority.
MEDIA AND BUSINESS INQUIRIES
62. Business Inquiries
Until Hostwover publishes a dedicated business contact, general business inquiries may be sent to:
Suggested subject:
Business Inquiry – [Topic]
63. Partnership Inquiries
Potential partnership or commercial inquiries may currently be routed through:
Hostwover may introduce a dedicated business contact later.
64. Media Requests
Media or press requests may currently be sent to:
Suggested subject:
Media Inquiry – [Organization / Topic]
Hostwover may establish a separate media contact in the future.
COMPANY INFORMATION
65. Registered Legal Name
Hostwover's exact registered legal name should be displayed here after verification against official business records:
Registered Legal Name:
`[INSERT VERIFIED REGISTERED LEGAL NAME]`
66. Legal Form
Legal Form:
`[INSERT VERIFIED LEGAL FORM]`
For example, the actual registered business form should be shown rather than assumed.
67. Commercial Registration
Commercial Registration Number:
`[INSERT VERIFIED COMMERCIAL REGISTRATION NUMBER]`
Do not publish an assumed or placeholder number as though it were genuine.
68. Tax Registration
Tax Registration Number:
`[INSERT VERIFIED TAX REGISTRATION NUMBER]`
69. VAT Registration
VAT Registration Number:
`[INSERT VERIFIED VAT REGISTRATION NUMBER IF APPLICABLE]`
70. Business Address
Registered / Principal Business Address:
`[INSERT VERIFIED BUSINESS ADDRESS]`
The public address should correspond to Hostwover's actual legally appropriate business contact or registered address.
71. Telephone
Official Telephone Number:
`[ADD ONLY IF HOSTWOVER HAS AN OFFICIAL PUBLIC BUSINESS NUMBER]`
A personal or temporary telephone number should not be presented as Hostwover's permanent legal contact unless intentionally designated for that purpose.
72. No Invented Contact Details
Hostwover should not publish invented:
- physical addresses.
- telephone numbers.
- registration numbers.
- tax numbers.
- DPO identities.
- legal officers.
- abuse addresses.
- security addresses; or
- regulatory contacts.
Only active and verified details should be published.
EMAIL SECURITY
73. Verify Hostwover Emails
Official Hostwover communications should originate through Hostwover-authorized domains or communication systems.
Customers should exercise caution with messages claiming to represent Hostwover while requesting:
- passwords.
- card security codes.
- cryptocurrency payments.
- private keys.
- remote access; or
- unusual urgent payments.
74. Hostwover Will Not Ask for Your Password by Email
Hostwover personnel should not require Customers to disclose their Hostwover account password through ordinary email.
75. Authentication Codes
Do not send:
- one-time passwords.
- MFA codes.
- recovery codes; or
- other login verification secrets
unless an official secure Hostwover workflow specifically requires the information.
76. SSH Keys
Never send an SSH private key through an ordinary support message.
If temporary server access is legitimately needed, use a restricted temporary access mechanism where possible.
77. API Keys
Do not send full production API secrets unless Hostwover specifically instructs you to rotate or provide a temporary credential through an appropriate secure process.
78. Suspicious Communications
If you receive a message that appears to impersonate Hostwover, contact:
Suggested subject:
Possible Hostwover Impersonation
Do not reply to the suspicious sender with sensitive information.
RESPONSE AND COMMUNICATIONS
79. Response Times
Hostwover seeks to review communications within a commercially reasonable period.
Response times depend on:
- request type.
- severity.
- verification requirements.
- complexity.
- ticket volume.
- Service.
- provider involvement; and
- other circumstances.
Unless an applicable SLA expressly states otherwise, this page does not establish a guaranteed response time.
80. Urgent Requests
Marking every request as urgent may interfere with appropriate priority handling.
"URGENT" should be reserved for genuinely significant matters such as:
- active Service compromise.
- severe security vulnerability.
- serious abuse.
- critical production failure; or
- other time-sensitive high-impact issues.
81. Duplicate Requests
Please avoid submitting the same issue repeatedly through multiple channels.
Hostwover may combine duplicate requests into a single case.
82. Existing Ticket
If a ticket already exists, reply to that case or include its reference rather than creating unnecessary duplicate requests.
83. Attachments
Attachments may be useful for:
- screenshots.
- logs.
- invoices.
- technical evidence.
- legal documents; and
- abuse reports.
Only include information reasonably necessary to resolve the issue.
84. File Security
Do not send executable malware or unsafe files through ordinary support channels.
For security investigations, coordinate with Hostwover before transmitting potentially dangerous samples.
85. Language
Hostwover may provide communication in English, Arabic, or other supported languages depending on channel and availability.
Availability of translated website content does not guarantee that every specialized request can be handled immediately in every language.
86. Accurate Contact Information
Customers are responsible for maintaining current contact information within their Hostwover account.
Important notices may concern:
- renewals.
- domain expiration.
- billing.
- security.
- abuse.
- verification.
- suspension.
- legal matters; or
- Service changes.
87. Email Delivery
Hostwover cannot guarantee that every message sent to a Customer will avoid:
- spam filtering.
- mailbox quotas.
- provider blocking.
- address errors; or
- other external email-delivery issues.
Customers should keep their account email valid and monitored.
88. Independent Contact Email
For important domain accounts, Customers should consider maintaining a contact email that does not depend solely on the same domain being managed.
This reduces the risk of losing access to important communications if the domain itself expires or experiences DNS problems.
CONTACT DIRECTORY
89. Current Contact Directory
Until dedicated channels are officially established, the current Hostwover contact directory is:
- General Support — [email protected].
- Technical Support — [email protected].
- Billing — [email protected].
- Refunds — [email protected].
- Domains — [email protected].
- Web Hosting — [email protected].
- VPS — [email protected].
- VDS — [email protected].
- Professional Email — [email protected].
- Google Workspace — [email protected].
- Privacy / Data Protection — [email protected].
- Abuse — [email protected].
- Security Vulnerabilities — [email protected].
- Copyright — [email protected].
- Trademark — [email protected].
- Domain Disputes — [email protected].
- General Legal Communications — [email protected].
Website: hostwover.com
90. Future Specialized Channels
Hostwover may later establish specialized channels such as:
- Abuse — `[email protected]`.
- Security — `[email protected]`.
- Privacy — `[email protected]`.
- Legal — `[email protected]`.
These addresses should only appear as active contact methods after they have actually been:
- created.
- secured.
- monitored.
- tested; and
- incorporated into the relevant Hostwover procedures.
RELATED POLICIES
91. Customer Service Policy
General support procedures are governed by the:
Hostwover Customer Service Policy
92. Privacy Policy
Personal Data practices are explained in the:
Hostwover Privacy Policy
93. Privacy & Data Protection Policy
Privacy governance and Data Subject procedures are further described in the:
Hostwover Privacy & Data Protection Policy
94. Abuse Handling Policy
Abuse-reporting procedures are governed by the:
Hostwover Abuse Handling Policy
95. Responsible Disclosure Policy
Security researchers should follow the:
Hostwover Responsible Disclosure Policy
96. Trademark & Copyright Policy
Intellectual property complaints should follow the:
Hostwover Trademark & Copyright Policy
97. Domain Dispute Policy
Domain ownership and trademark-control disputes should follow the:
Hostwover Domain Dispute Policy
98. Refund Policy
Refund requests remain subject to the:
Hostwover Refund Policy
99. Legal Information
Hostwover's broader legal and business disclosure framework is provided in:
Hostwover Legal Information
100. Formal Service and Statutory Contact Information
Once Hostwover's verified legal entity details are ready for publication, this page should be updated to include the legally appropriate:
- registered legal name.
- legal form.
- Commercial Registration number.
- tax registration information.
- VAT information where applicable.
- registered or principal business address.
- formal legal-service contact; and
- other legally required business disclosures.
Until those details are verified, Hostwover should not replace them with assumptions.
101. Changes to Contact Information
Hostwover may update its contact channels as the business and Services develop.
Changes may include:
- dedicated departments.
- new email addresses.
- support portals.
- telephone support.
- legal contacts.
- privacy contacts.
- abuse portals.
- security reporting systems; or
- other communication methods.
102. Current Information Controls
Where this page and an older Hostwover page display different contact information, Customers should use the most recently published official contact information after confirming that the newer channel is genuine.
103. Fraudulent Contact Details
A third-party website or person publishing an email address, phone number, payment account, or messaging account while claiming that it belongs to Hostwover does not make that channel an official Hostwover contact.
Customers should verify important requests through hostwover.com.
104. No Social-Media Account Recovery
Public social-media messages should not be used for sensitive actions such as:
- account recovery.
- domain ownership changes.
- refund redirection.
- disclosure of Customer information; or
- security verification
unless Hostwover expressly provides a secure authenticated process through that channel.
105. Definitions
For purposes of this page:
- "Customer" means a person or organization purchasing, administering, accessing, or using a Hostwover Service.
- "Hostwover" means the Hostwover brand and, where applicable, the verified legal person or entity operating the relevant Service.
- "Personal Data" means information protected as personal data or personal information under applicable privacy law.
- "Service" means a product, subscription, functionality, or service provided, sold, resold, managed, or made available through Hostwover.
- "Support" means Hostwover's Customer assistance functions.
106. Contact Principles
Hostwover's contact framework is based on these principles:
- Customers should have a clear way to reach Hostwover.
- Sensitive account matters should use authenticated channels where possible.
- Requests should be routed according to their subject.
- Customers should not be asked to send unnecessary passwords or security secrets.
- Privacy requests should be verified appropriately.
- Abuse reports should contain actionable evidence where available.
- Security researchers should follow the Responsible Disclosure Policy.
- Copyright and trademark complaints should contain sufficient supporting information.
- Domain ownership disputes should use the appropriate dispute process.
- Formal legal service should not be confused with ordinary Customer Support.
- Dedicated addresses should not be advertised until they actually exist and are monitored.
- Hostwover should not invent business addresses, telephone numbers, DPO information, or legal contacts.
- Urgent requests should receive appropriate prioritization based on actual risk.
- Customers should maintain accurate account contact information.
- Hostwover should update this page whenever an official contact channel materially changes.
107. Primary Contact
At present, Hostwover's primary public contact is:
Hostwover Support
Email: [email protected]
Website: hostwover.com
108. Information Still Required Before Final Statutory Publication
The following information should be inserted once verified:
Registered Legal Name:
`[REQUIRED]`
Legal Form:
`[REQUIRED]`
Commercial Registration Number:
`[REQUIRED IF APPLICABLE]`
Tax Registration Number:
`[REQUIRED IF APPLICABLE]`
VAT Registration Number:
`[REQUIRED IF APPLICABLE]`
Registered / Principal Business Address:
`[REQUIRED]`
Official Public Telephone:
`[OPTIONAL – ADD ONLY IF DESIGNATED]`
Formal Legal-Service Contact:
`[VERIFY BEFORE PUBLISHING]`
Privacy / DPO Contact:
`[ADD WHEN APPLICABLE AND VERIFIED]`
These details must not be fabricated.
109. Effective Date
This Contact Information page is effective from the date stated above.
It should be reviewed whenever Hostwover:
- creates a new official contact channel.
- changes its business address.
- changes its legal entity.
- establishes a dedicated legal contact.
- establishes a dedicated privacy or DPO contact.
- establishes dedicated abuse or security channels; or
- otherwise materially changes how Customers and third parties should contact Hostwover.
END OF CONTACT INFORMATION