Email Infrastructure & Domain Registry
Relevant source files
The following files were used as context for generating this wiki page:
The Email Infrastructure and Domain Registry modules define the authoritative configuration for the project's digital presence and communication channels. These modules establish the primary and secondary domains, manage Domain Name System (DNS) records, and configure secure email routing protocols.
This system ensures that the Imperial Archive maintains a "LOCKED_CANONICAL" state for its digital identity. It integrates registrar services with DNS protection and advanced email security headers to prevent unauthorized spoofing or data loss.
Domain Registry Architecture
The domain registry manages two distinct domains with specific operational purposes. The primary domain, imperialarchive.ai, handles main cognitive and system functions. The secondary domain, imperialarchive.com, is restricted to email-only operations. Both domains use Epik.com as the registrar and Cloudflare for DNS management.
Entity Relationship Diagram
The following diagram illustrates the relationship between the governing company, the registrars, and the specific domain entities.
Domain Asset Configuration
| Domain ID | FQDN | TLD | Purpose | Status |
|---|---|---|---|---|
| IA-DOMAIN-MAIN | imperialarchive.ai | .ai | Primary System Hub | Active |
| IA-DOMAIN-EMAIL | imperialarchive.com | .com | Email-only Domain | Active |
Sources: 02_REPOSITORY/domain-registry.yml:7-21
Email Infrastructure
The email infrastructure implements a restricted routing model for internal and security-related communications. It defines specific high-priority addresses and mandates a "reject" policy for DMARC to maintain strict security.
Email Security Flow
The system uses three layers of verification to validate outbound mail. SPF validates the sending server, DKIM provides a cryptographic signature, and DMARC dictates how receiving servers handle failures.
Defined Email Addresses
Email addresses are classified by priority. The routing for these addresses is marked as "RESTRICTED" and they are not intended for public visibility.
- founder@imperialarchive.com: High Priority (Founder access)
- security@imperialarchive.com: High Priority (Security reporting)
- info@imperialarchive.com: Medium Priority (General inquiries)
Sources: 02_REPOSITORY/domain-email.yml:9-12
DNS and Subdomain Management
The DNS layer uses Cloudflare nameservers to manage apex records and subdomains. Subdomains are deployed in three phases to support growing project requirements.
Subdomain Deployment Phases
| Phase | Label | Purpose | Status |
|---|---|---|---|
| Phase 1 | www | Primary web portal | Planned |
| Phase 1 | tamara | Tamara Learning Program | Planned |
| Phase 1 | security | Security documentation | Planned |
| Phase 2 | docs | Technical documentation | Planned |
| Phase 2 | elias | Elias project space | Planned |
| Phase 3 | api | External interface | Future |
Sources: 02_REPOSITORY/domain-subdomains.yml:8-16
Security Records Configuration
The system requires specific DNS records to be published once providers are configured.
recommended_security_records:
spf:
value: "v=spf1 include:_spf.google.com ~all"
note: "Do NOT publish until email provider is configured."
dmarc:
initial_value: "v=DMARC1; p=none; rua=mailto:security@imperialarchive.com"
final_value: "v=DMARC1; p=reject; rua=mailto:security@imperialarchive.com"
caa:
value: "0 issue \"letsencrypt.org\""
Sources: 02_REPOSITORY/domain-dns.yml:14-30
Financial and Operational Status
Infrastructure maintenance involves annual recurring costs for the .ai and .com registries, alongside variable monthly costs for Cloudflare tiers.
- Total Annual Minimum: $45 USD (Domain renewals)
- Total Annual Maximum: $525 USD (Including Cloudflare Pro services)
- Registry Status: Registered and Active
- DNS Status: Pending Propagation
Sources: 02_REPOSITORY/domain-costs.yml:7-22, 02_REPOSITORY/domain-registry.yml:37-43
The infrastructure is currently in a state of "DEGRADED" health for domain and security segments because DNS delegation and two-factor authentication on registrar accounts are still "pending" implementation.
Sources: 02_REPOSITORY/health.yml:19-20, 02_REPOSITORY/domain-registry.yml:40-43