A record
Points a name to an IPv4 address, commonly used for a website’s root domain.
Quick definitions, practical checks, and direct SaaSTech account instructions for common DNS tasks.
Use these lookups after saving records to see what the internet can retrieve. They diagnose published records; they do not know the tenant-specific values your provider intended.
Confirm which mail servers and priorities are publicly visible.
Run external check ↗Find the published SPF record and flag syntax or lookup problems.
Run external check ↗Confirm the public DKIM key is retrievable for a domain and selector.
Run external check ↗Parse the published DMARC policy and highlight configuration errors.
Run external check ↗Run DNS, SMTP, reputation, and blacklist diagnostics in one place.
Run external check ↗Use these official SaaSTech guides for the exact control-panel steps. Build and review the record values here first.
Points a name to an IPv4 address, commonly used for a website’s root domain.
Points a name to an IPv6 address.
Makes one hostname an alias of another. A CNAME normally cannot share the same host with other record types.
The system that translates domain names into destinations used by websites, email, and other services.
A mail signature published in DNS that helps receiving systems verify outgoing email.
A policy and reporting record that tells receivers what to do when SPF or DKIM checks fail.
The portion of the domain a record applies to. @ commonly means the root domain.
Directs incoming email. Lower priority numbers are usually preferred first.
Identify the provider that hosts the authoritative DNS zone.
The period while DNS resolvers refresh cached information after a change.
A single TXT policy identifying systems allowed to send mail for a domain.
How long resolvers can cache a DNS answer before checking again.
Check that MX, SPF, DKIM, and DMARC records were preserved. If nameservers changed, compare the new zone with the dated backup.
Copy the TXT host and value exactly, check whether the DNS manager automatically appends the domain, and allow the current TTL to pass.
Check both root and www records, wait through the old TTL, and test from a different network before editing again.
Confirm the website records are correct and that conflicting CAA, proxy, or duplicate host records are not blocking certificate issuance.
Confirm there is one valid SPF record covering all senders, DKIM passes, and DMARC is configured appropriately.
Pause. Compare the host and type carefully, use the DNS Builder, and remove a record only when the provider explicitly requires replacement.
Roll back or contact support when a critical website, email, payment, authentication, or customer service fails and the cause is not immediately clear.