DNS Lookup
A, AAAA, MX, NS, TXT, SOA and CAA records.
Records for appextech.com
| Type | TTL | Value |
|---|---|---|
| A | 131s | 172.67.201.55 |
| A | 131s | 104.21.85.25 |
| AAAA | 147s | 2606:4700:3033::ac43:c937 |
| AAAA | 147s | 2606:4700:3037::6815:5519 |
| MX | 263s | priority=5 _dc-mx.24309b3ad77e.appextech.com |
| MX | 263s | aspmx.l.google.com |
| NS | 86400s | james.ns.cloudflare.com |
| NS | 86400s | isla.ns.cloudflare.com |
| TXT | 263s | v=spf1 a:appextech.net ip4:173.249.40.14 ip4:144.91.71.114 ip4:144.91.71.113 include:_spf.google.com ~all |
| TXT | 263s | google-site-verification=Ntia4dp0owZYjUV0IiR5VhRcBxOmedYwiFMS4vxLZ00 |
| SOA | 1763s | mname=isla.ns.cloudflare.com rname=dns.cloudflare.com serial=2406137234 |
| CAA | 3600s | issue "ssl.com" |
| CAA | 3600s | issue "digicert.com; cansignhttpexchanges=yes" |
| CAA | 3600s | issue "comodoca.com" |
| CAA | 3600s | issuewild "ssl.com" |
| CAA | 3600s | issue "letsencrypt.org" |
| CAA | 3600s | issuewild "comodoca.com" |
| CAA | 3600s | issuewild "digicert.com; cansignhttpexchanges=yes" |
| CAA | 3600s | issue "pki.goog; cansignhttpexchanges=yes" |
| CAA | 3600s | issuewild "pki.goog; cansignhttpexchanges=yes" |
| CAA | 3600s | issuewild "letsencrypt.org" |
About DNS Lookup
This DNS lookup queries every common record type in one pass: A and AAAA for IPv4 and IPv6 addresses, MX for mail servers, NS for the authoritative nameservers, TXT for verification strings and SPF, SOA for the zone start of authority, CAA for certificate authority restrictions, and CNAME aliases. Each record returns with its time-to-live so you can see how long resolvers will cache the answer.
When to use it
Check this tool right after changing DNS at your registrar to confirm the new records are visible from the public resolver chain. Use it to compare what a candidate hosting provider's nameservers return versus your current setup. Sysadmins also rely on it to verify CAA records before issuing a new TLS certificate, since a misconfigured CAA can block Let's Encrypt and other CAs from issuing.
How to read the results
TTL values in seconds tell you how long a change will take to propagate after you reduce it. A records hold IPv4 addresses, AAAA holds IPv6. MX records show priority then target, lowest priority wins. NS records list the authoritative nameservers, which should match what your registrar shows. A missing CAA record means any public CA can issue certificates, which is often fine but worth knowing.
Frequently asked questions
Why do I see multiple A records for one hostname? ▾
Multiple A records mean DNS round-robin. The resolver picks one each query, spreading traffic across the listed IPs. Large sites combine this with anycast for redundancy and load distribution across regions.
What is the difference between an A and a CNAME record? ▾
An A record points directly to an IP address. A CNAME points to another hostname, which then resolves to an A record. CNAMEs cannot coexist with other records on the same name, including the apex.
How long until my DNS changes show up here? ▾
It depends on the TTL of the previous record. If the old TTL was 3600 seconds, expect up to an hour for caches to flush. New records with a low TTL appear quickly once the authoritative server returns them.
What does the SOA record tell me? ▾
The Start of Authority record holds the primary nameserver for the zone, the admin contact email (with dots instead of @), serial number, refresh and retry intervals, and minimum TTL. The serial increments on every zone change.