Domain Mapping
Record every fully qualified domain name, associated virtual host, and canonical redirect rules. Include DNS TTL expectations and owner contact to prevent misrouting and accelerate troubleshooting during propagation problems.
A clear Hosting vHost Document reduces deployment errors, clarifies operational responsibilities, and provides an auditable record for security and compliance reviews. When signed electronically, it documents consent and assignment of responsibilities in a format admissible under ESIGN and UETA where applicable.
Organizations that manage web infrastructure, including hosting providers, internal IT teams, and DevOps contractors, commonly use the Hosting vHost Document.
The document aligns technical configuration with contractual duties so both operations and legal teams share a consistent reference during deployment and incidents.
| Field | Configuration |
|---|---|
| Domain Settings | List FQDNs and map to vHost root paths |
| SSL Setup | Specify cert type, issuer, and expiration dates |
| Access Control | Define SSH users, roles, and MFA requirements |
| Deployment Trigger | Approval status or CI/CD job name for deployment |
Record every fully qualified domain name, associated virtual host, and canonical redirect rules. Include DNS TTL expectations and owner contact to prevent misrouting and accelerate troubleshooting during propagation problems.
Specify certificate type, CA issuer, key rotation schedule, renewal responsibilities, and whether automation (ACME) is active. Track expiration dates to avoid outages and security incidents.
List server directives, port bindings, rewrite rules, and resource limits. Note environment-specific differences (staging vs production) and any module dependencies required for correct behavior at runtime.
Define log locations, retention windows, and monitoring thresholds. Specify alerting recipients, escalation paths, and integration points with SIEM or incident response systems for security and reliability.
Describe backup frequency, retention policy, backup encryption, and restoration steps including test procedures. Assign responsible parties and RTO/RPO targets to align with SLA commitments and recovery objectives.
Track document versions, change history, approver signatures, and deployment artifacts. Require change requests for configuration updates and retain an immutable copy of each accepted vHost configuration.
Date when terms commence; use MM/DD/YYYY.
Record expiration date and renewal deadline.
Scheduled downtime windows for updates and patches.
Periodic review every 6 or 12 months.
Record retention period and audit access rights.
Author compiles technical and legal information.
Technical review of configs and security settings.
Confirm liabilities, SLA language, and retention terms.
Execute changes in production and log actions.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |