Wildcard support and verification differ by platform. Check the current official instructions before publishing *.example.com and avoid broad wildcards when a narrow hostname is enough.

Source checked 11 August 2026: Google Workspace official documentation.

A normal connection should require domain-control proof, not public disclosure of private account data. Use RDAP for registration data and expect lawful redaction of personal fields.

Source checked 11 August 2026: Google Workspace official documentation.

The URSY truth-spine source for Google Workspace is https://support.google.com/a/answer/87127. Check the live page before making production DNS changes.

Source checked 11 August 2026: Google Workspace official documentation.

Compare the host’s expected records with authoritative DNS, remove conflicts, check certificate status, test both apex and www, and retain a dated evidence note of every change.

Source checked 11 August 2026: Google Workspace official documentation.

Lower TTL in advance, attach and verify the hostname where possible, reproduce mail and verification records, change the minimum DNS records, monitor both endpoints, then remove the old service only after expiry of caches.

Source checked 11 August 2026: Google Workspace official documentation.

Verify one canonical HTTPS host, 301 redirects, robots.txt, XML sitemaps, structured data, Search Console ownership, analytics continuity and that preview URLs are not being indexed.

Source checked 11 August 2026: Google Workspace official documentation.

Keep the previous DNS values and provider access, avoid deleting the former service during propagation, document the change time, and restore the prior authoritative records if health checks fail.

Source checked 11 August 2026: Google Workspace official documentation.

Monitor DNS answers, HTTP status, redirect chains, TLS expiry, canonical tags and mail authentication separately. Alert on changes at the authoritative nameservers, not only a local resolver.

Source checked 11 August 2026: Google Workspace official documentation.

Google Workspace — Google currently documents MX priority 1 to smtp.google.com for newer setups; older tenants may retain legacy aspmx records.

Source checked 11 August 2026: Google Workspace official documentation.

Google Workspace supports root-domain connections, but the exact record type and value depend on the product. Follow https://support.google.com/a/answer/87127 and use the live values shown there.

Source checked 11 August 2026: Google Workspace official documentation.