REAL NAME.COM SANDBOX RECOVERY

From DNS drift to independently verified recovery.

This walkthrough mirrors the recovery that was actually executed and preserved in the live DomainTwin workspace: detect the drift, score the evidence, preview one deterministic rollback, require human approval, execute through Name.com Sandbox and prove the provider matches the trusted snapshot.

View verified recovery Open live workspace

PERSISTED RECOVERY EVIDENCE

Incident #8

CRITICAL · 75/100

DETECTED DRIFT

A www no longer matched the trusted snapshot

75/100

KNOWN-GOOD203.0.113.10

→

OBSERVED198.51.100.77

DNS DRIFTDETECTEDHTTPFAILEDINCIDENTCREATED

DETERMINISTIC INCIDENT EVIDENCE

Why DomainTwin scored the incident CRITICAL

EXPLICIT FACTORS

+30ADDRESS_RECORD_CHANGED

+30HTTP_HEALTH_FAILED

+15UNKNOWN_DESTINATION

=75CRITICAL incident score

The core decision is deterministic. The optional AI layer may explain evidence, but it never controls DNS authority.

RECOVERY PLAN #8

One exact rollback operation

HUMAN APPROVED

ActionRecordCurrentRestore

UPDATEA www198.51.100.77203.0.113.10

Known-good snapshot v3 · exact preview · explicit approval · Name.com Sandbox execution

PROVIDER VERIFICATION

Recovery #8 is proven by a fresh Name.com read

RECOVERED

EXPECTEDa3b35ae640…dad54313

ACTUALa3b35ae640…dad54313

FINGERPRINTMATCH YES

DNS DRIFTFALSE

Post-recovery monitoring remains DEGRADED at 30/100 because this sandbox domain has no real HTTP service. DNS itself is restored, verified and no new incident is created.

LIVE PRODUCT WORKSPACE

Inspect the same Incident #8 and Recovery #8 in the deployed control plane.

The public judge account is intentionally read-only. Continuous monitoring remains active, while DNS mutation and emergency registration permissions stay disabled in the public deployment.

Open live workspace Judge login