TXT records of brewstack.com.
Every TXT record of a name, joined into one line each and labelled: mail rules, ownership proofs for other services, and the rest.
Looking up…
What TXT records are for.
TXT records hold free text. In practice they do two jobs: they carry mail rules (SPF, DMARC, DKIM keys) and they prove to other services that you control the domain. A service gives you a token, you publish it, the service looks it up.
Long records come in pieces.
One piece of a TXT record holds at most 255 characters, so long values such as DKIM keys are split into several quoted strings. Mail software joins them with nothing in between, and this page shows them joined the same way. The quotes and the splits you see in your DNS host are normal.
Only one SPF record.
A domain must publish a single record starting with v=spf1. Two of them is a permanent error: receivers may treat all your mail as unauthenticated. Merge them into one, listing every service that sends for you, and keep it under 10 lookups (each include: counts).
Where the other mail records live.
- DMARC: at
_dmarc.example.com. - DKIM keys: at
selector._domainkey.example.com, where the selector is thes=value in a message's DKIM-Signature header. - MTA-STS at
_mta-sts., TLS reporting at_smtp._tls., BIMI atdefault._bimi.
Old verification tokens.
Tokens for services you no longer use can go. Keep the ones still in use: Google, for one, checks its Search Console token again later and asks you never to remove it after verifying.
Questions people ask.
What is a TXT record?
A TXT record holds text attached to a domain. It is mostly used for email rules (SPF, DKIM, DMARC) and to prove domain ownership to services such as Google or Microsoft.
How do I check a domain's TXT records?
Type the domain, or a subdomain such as _dmarc.example.com. Every TXT record is shown joined into one line and labelled by what it does.
Can a domain have more than one TXT record?
Yes, as many as it needs. The exception is SPF: a domain must have exactly one record starting with v=spf1.
Why is my TXT record split into several strings?
One string in a TXT record holds at most 255 characters, so long values are split. Mail software joins the pieces again, so the split is normal.
Hivex index
Short names, still free to register.
Starting something new? Hivex keeps a live index of short, brandable .si names nobody has claimed yet, each checked with the registry.
From code, or an AI assistant.
The same lookup is a free JSON API, with no key and open CORS, and a tool any AI assistant that speaks MCP can call.
curl "https://hivex.si/api/v1/tools/dns?name=brewstack.com&type=TXT"More DNS tools
- DNS lookupAll records at once: A, AAAA, CNAME, MX, NS, TXT, CAA, SOA.
- MX lookupMail servers in priority order, the provider, SPF and DMARC at a glance.
- NS lookupName servers, the DNS host, SOA settings, and marketplace parking.
- CNAME lookupThe full alias chain, the final addresses, and the platform behind it.
- CAA lookupAllowed certificate authorities, wildcard rules and report addresses.
- DNS propagation checker13 public resolvers side by side, with how long each keeps its copy.
- Reverse DNSThe PTR hostname of an IPv4 or IPv6 address, checked both ways.
- DNS health checkEvery name server asked directly: one report, every check.
- DNSSEC checkerDS, keys and validation: where the chain of trust holds or breaks.
- Subdomain finderSubdomains from certificate logs, DNS and the archive.
- DNS historyPast IP addresses and hosts, from passive DNS.
- DNS setup helperThe records each platform asks for, checked live.
- Domain checkerIs a name free to register? Checked live on any extension.
Sources
- RFC 1035: Domain names, implementation and specification, section 3.3.14
- RFC 7208: Sender Policy Framework (SPF)
- RFC 7489: DMARC
- RFC 6376: DomainKeys Identified Mail (DKIM)
- Google Search Console: verify site ownership
By Hivex. Updated 10 October 2026. Lookups run live through Cloudflare's public resolver and are kept for at most five minutes.