Domain trust alone is not enough
HTTPS answers whether a certificate is authorized for a domain name. The tempting assumption is that this is enough to trust the machine on the other end of the connection. It fails when DNS is hijacked, a registrar pat
HTTPS answers whether a certificate is authorized for a domain name. The tempting assumption is that this is enough to trust the machine on the other end of the connection.
It fails when DNS is hijacked, a registrar path is abused, or validation still succeeds while traffic terminates on an attacker-controlled host. The client can see a valid domain certificate and still not be talking to an authorized server.
We wrote up Double Sign (Double Certificate Authority): require a second, independent cryptographic authorization for the node β not only the domain β before the client accepts the connection.
AL'S-OPS LLC is a Utah company building privacy-first infrastructure software.
What changed
- Domain authentication stays on the usual Web PKI path (TLS certificate for the name).
- Node authentication is a separate credential binding a server key to an authorized IP, service, or node identity, validated against a trust anchor that is not the domainβs DNS or registrar path.
- The server must prove possession of the private key.
- Both paths must succeed. Domain-valid without node-valid is a reject. Node-valid does not authorize an unrelated domain.
- Trust anchor design separates a long-lived offline root from delegated operational keys, with signed epoch metadata, revocation, and anti-rollback patterns in the spirit of systems like The Update Framework (TUF).
- Baseline operational policy uses monthly trust epochs for credential renewal (and preferably key rotation), while compromised keys remain revocable immediately.
The real problem
Proving control of a domain is not the same as proving authorization to operate the server that claims to represent that domain. A single validation path tied to DNS and registrar infrastructure is a single place that path can fail open for the attacker.
Double Sign is meant to force a second defeat: the attacker needs a valid node credential and private key, not only a domain certificate that looks legitimate.
What we are not doing
- Replacing TLS, Certificate Transparency, RPKI, or DANE β those solve different parts of the problem.
- Claiming browser-wide deployment or a shipped product feature in this note.
- Treating a second signature as meaningful if it depends on the same administrators, DNS path, or trust root as the first.
- Inventing customers, fleet size, or adoption metrics.
Domain identity and server authorization should not share one quiet point of failure. If the second signature is not independent, it is not a second signature.
Originally published on the Al's-Ops blog.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.