A client blamed you for a DNS change. Prove it was not you.

A client's site stops loading, or their mail starts bouncing. They do not know whether it was their registrar, an expired certificate, a provider on their side, or something you touched. They know it broke, and they know you are the one who works on their infrastructure. So the call, and the assumption, lands on you. Without a record, it is your word against a bad day.

Why the call lands on you

The people who get blamed for a domain breaking are rarely the ones who broke it. A managed service provider, an agency or an internal team holds the keys, so when anything about a domain shifts, they are the obvious suspect. Proving a negative, that you did not make a change, is hard in the moment: the records a registrar or a provider keeps are theirs, not yours, and they show the current state, not what it was the hour before the outage.

What actually settles it: a dated reading of the domain

What ends the argument is a reading of the domain taken from the outside, before and after, that nobody in the room controls. DomainDrift watches a domain's public surface continuously, its DNS records, the certificates in the public transparency logs, its mail setup and the host behind it, and records every change with the date and time it was seen. When a client says "you changed the nameservers Tuesday night", you can show the signed reading from Tuesday morning and the one from Wednesday, and point at the line that did, or did not, move.

Read the domain right now, free

You do not need an account or anything installed to start. Type the domain into the keyless reader and it is pulled apart in a few seconds: who runs it, who carries its mail, whether the certificate is healthy, each line a reading taken and signed the moment it was made. That is the same reading the client's own team can check against our published keys, so a finding you raise stands on the record rather than on your word.

A signature proves who took a reading and that it has not changed since; the chain anchor proves when it existed. Whether a configuration is correct stays a separate question you check yourself, against keys we publish. Signing is added trust. See how to verify.

Keep the record, so the next dispute is a link

The free reading answers today's question. The value for anyone who answers for other people's domains is the standing record: a watch across every client estate that keeps the dated history going, and an alert that names the client the moment a nameserver, a certificate or a mail record moves, before they call you. If you run many clients' domains under one roof, that is what the managed service provider watch is built for, and the full picture is on the solutions page.

Type any domain at domaindrift.io and watch its DNS, mail, certificate and hosting get read apart, signed and dated. Looking is free; keeping the dated record is an account.