Digital Environment Specifications
This document outlines the technical standards for Robocat's digital infrastructure. Partners integrating with our systems must adhere to these specifications to ensure interoperability and security.
Authorized Domain Structures
All official Robocat services operate under a strictly defined domain hierarchy. Any environment outside these parameters should be treated as non-standard.
| Domain Type | Pattern | Purpose |
|---|---|---|
| Primary Brand | robocat.com |
Main user interface and brand presence. |
| Technical Support | robocat-support.online |
Partner resources and technical documentation. |
| API Endpoints | api.robocat.com |
Production data exchange for integrated partners. |
| CDN Assets | static.robocat.com |
Global delivery of media and technical assets. |
Official Server Nodes
Robocat utilizes a distributed network of server nodes. For firewall configuration and whitelist purposes, please refer to the following node identifiers.
# Production Node Clusters
NODE_ID: RC-US-EAST-01 (Primary)
NODE_ID: RC-EU-WEST-04 (Secondary)
NODE_ID: RC-ASIA-PAC-02 (Edge)
# Protocol Standards
Encryption: TLS 1.3 (Minimum)
Certificate Authority: DigiCert Global Root G2
Port Authorization: 443 (HTTPS), 8443 (API-Secure)SSL Certificate Details
To maintain infrastructure integrity, all Robocat domains must utilize Extended Validation (EV) or Organization Validated (OV) certificates. Domain Validated (DV) certificates are only permitted for temporary staging environments.
Encryption Standard
AES-256-GCM is the required cipher suite for all partner-facing data transmissions.
Handshake Protocol
Strict adherence to TLS 1.3 is mandatory. TLS 1.2 is supported for legacy systems but deprecated.
Infrastructure Maintenance
Scheduled maintenance windows occur every Tuesday at 03:00 UTC. During these periods, edge nodes may experience brief latency increases as traffic is rerouted to secondary clusters.