Launch readiness report: is it safe to switch DNS?

Create and share a report

1. Run the checks first

   Run a QA report and a visual compare on the link. The readiness report uses the latest finished run of each.

2. Open Launch readiness

   On the Links page, click Readiness on the link (or open the link settings and choose Launch readiness). The page shows a live check that only your team can see.

3. Create a shareable report

   Click Create shareable report. DNSPeek saves a snapshot and copies its link. Send the link to your client; they don’t need an account.

Launch readiness reports are part of the Pro, Agency and Provider plans. On Agency and above the page carries your report branding: logo, colour, footer and contacts.

How the verdict is decided

The rules are fixed, so the same data always gives the same answer.

• Not ready: no finished QA report, a critical QA finding, or a page that differs more than 5% from the live site in the visual compare.
• Ready with warnings: QA warnings, a QA report older than 7 days, a page that differs 1–5% or could not be captured, no visual compare yet, open client comments, no client approval yet (when comments are on), or no valid certificate for the domain on the new server.
• Ready to launch: none of the above.

DNS status is shown for information only: before the switch, the domain still points to the current server, which is expected. When the client has approved the launch through client comments, the report names who approved it and when, right under the verdict.

Readiness at a glance

The link's page shows the readiness next to its title, for example Ready to switch, Ready with warnings · 2 issues, Not ready · 1 blocker or Not checked yet (no finished QA report). Click it to open the full readiness page.

On Pro and above this is the verdict described above. On the Free plan it is a Quick check built only from what the plan already has: the server check of the link and your latest QA report. A failing server check or critical QA findings make it not ready; a server check with warnings, QA warnings or a report older than 7 days add warnings. It does not include the visual compare, client comments and approval or the certificate check, and it cannot be shared with a client.

What your client sees and how to stop sharing

• A snapshot: the shared page never changes. Create a new report after you fix something.
• Nothing internal: the page never shows the new server’s IP address, your team or email addresses. Screenshot links expire after 15 minutes; reloading the page renews them.
• Not indexed: search engines are told not to index report pages.
• Revoke any time: click Revoke next to a report. Within a minute, the link shows “not found”.
• Made private: making the link private revokes all its readiness report links the same way. Create a new report to share it again.

The page prints cleanly: use Save as PDF to attach it to an email. Ready to go? Continue with the migration playbook.