Infrastructure
A live cloud deployment with documented operational boundaries.
The public website and associated mail hostname are hosted on the same Kamatera infrastructure and form a controlled environment for administration, protocol testing, documentation, and security review.
| Component | Current role | Status |
|---|---|---|
| emailinfralab.com | Main public website and project identity | Live |
| mail.emailinfralab.com | Primary mail hostname for controlled lab operation | Live |
| 114.29.239.206 | Kamatera server IPv4 address | Active |
| Ubuntu | Server operating environment | Deployed |
| Nginx | HTTPS website delivery and web-server layer | Deployed |
| Stalwart Mail Server | Mail-system research and controlled service testing | Deployed |
| TLS certificates | Encrypted web and service transport | Installed |
| Reverse DNS / PTR | IP-to-hostname identity alignment | Provider review |
| Expanded monitoring | Metrics, logs, alerting, and capacity visibility | Planned |
| Extended recovery automation | Repeatable restore and disaster-recovery workflows | Planned |
Architecture layers
How the public environment is organized
Public identity, address records, mail routing, authentication records, and reverse-DNS alignment.
Kamatera compute, public IPv4 connectivity, host firewall policy, and controlled administrative access.
Ubuntu service management, security updates, user permissions, logs, storage, and time synchronization.
Nginx serves the public website over TLS and separates public content from administrative interfaces.
Stalwart supports controlled study of SMTP, mailbox services, authentication, queues, and operational behavior.
Documentation, validation, backup, security review, monitoring, incident response, and change control.
Operational boundaries
Designed for controlled administration and research
The infrastructure is not an open relay and is not offered for anonymous or third-party sending. Administrative access is restricted, public-facing services are intentionally limited, and changes are expected to be documented and validated.
Boundary controls
- No public SMTP relay access
- No sale or rental of server credentials
- No unauthorized bulk messaging
- No phishing, malware, or credential harvesting
- Abuse and security contacts published
- Provider requirements and applicable law respected