DNS
DNS-over-HTTPS lookup
Every record type, from one resolver or queried across all three at once. Queries go straight from your browser to the resolver — nothing reaches blackmesa.ca.
Lookup failed
Enter a domain to begin
Answered by instead of
Records
| Type | Name | Resolvers | Value | TTL |
|---|
About this data
- Records are fetched in your browser over DNS-over-HTTPS — Quad9 (9.9.9.9) by default, or Cloudflare, Google, or all three at once. Nothing is sent to blackmesa.ca.
- The DNSSEC verdict is the resolver’s own: it reports whether it validated the chain of trust from the root, so a validated answer means that resolver checked it, not that you did.
- TTLs are whatever each resolver reports, so a cached answer reads lower than the zone’s own value. In Query all, records are compared on their values only — differing TTLs are normal caching, not disagreement.
- Records are tagged by what they are for: MAIL (mail policy —
gathered from the apex and from
_dmarc,_mta-sts,_smtp._tlsanddefault._bimi), VERIFY (a SaaS vendor’s proof that you own the domain) and CERT (certificate issuance control — CAA, TLSA, ACME challenges). Verification records are matched against a list of what major vendors publish, so an unrecognised one is left untagged rather than guessed at.