Adding TXT Records

What are TXT records?

TXT records store text-based information in your DNS. They're not about your website itself — they're about proving things about your domain. Common uses include:

• Domain verification — proving you own the domain (Google Search Console, Facebook, etc.)
• Email authentication (SPF) — telling email servers which services can send email from your domain
• Email signing (DKIM) — adding a digital signature to outgoing emails
• Security policies (DMARC) — telling email servers what to do with suspicious emails from your domain

TXT records SiteGlowUp preserves automatically

When you migrate your DNS, we detect and preserve:

• SPF records — ensures your email keeps getting delivered
• DKIM records — maintains your email authentication
• Domain verification records — Google, Facebook, and other platform verifications stay intact
• DMARC records — your email security policy continues working

Adding a new TXT record

You can add TXT records directly from your dashboard — no support ticket needed:

1. Go to your dashboard and open the DNS section
2. Click Add DNS Record
3. Choose TXT as the record type
4. Enter the name (use @ for the root domain, or a subdomain like _acme-challenge)
5. Paste the exact value provided by the service requesting it
6. Leave TTL at the default (3600 seconds) unless the service asks for something specific
7. Save — the record goes live in Route53 within seconds

See Adding DNS Records for a full walkthrough of the form.

Common TXT record requests

Google Search Console verification

• Record: TXT on root domain (use @ for the name)


• Value: Provided by Google (starts with google-site-verification=)

Facebook domain verification

• Record: TXT on root domain (use @)


• Value: Provided by Facebook Business Manager

SPF for a new email service

• Existing SPF records must be merged, not replaced


• Don't add a second SPF TXT record — update the existing one so it lists every sending service

Important: don't replace — merge

A domain should only have one SPF record. If you're adding a new email service, the existing SPF value must be updated to include the new service, not replaced. If your dashboard already shows an SPF record on the root domain, email support before adding a new one — we'll help you merge them safely so existing mail keeps passing authentication.