CONTINUOUS INTERNET TELEMETRY24H DRIFT2,263 material changesacross 2,061 domains · +304 vs yesterdayDNS DRIFT19 domains changed DNS providertop destination cloudflare.comEMAIL DRIFT8 domains switched email providertop destination outlook.com · +5 vs yesterdayNOW3,916 curated domains not answering+487 vs yesterdayERRORS8,524 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT2,263 material changesacross 2,061 domains · +304 vs yesterdayDNS DRIFT19 domains changed DNS providertop destination cloudflare.comEMAIL DRIFT8 domains switched email providertop destination outlook.com · +5 vs yesterdayNOW3,916 curated domains not answering+487 vs yesterdayERRORS8,524 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block

quest.com

Observed 2026-07-15T12:01:40.178Z (7h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Email byMicrosoft 365
Registered withSafeNames Ltd.
Also usesMiroGoogle Search ConsoleAtlassianDockerSlack
18 subdomains · fortune_500
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat quest.com actually stands on - every host below is a signed observation
quest.com
A / AAAA
99.83.129.6875.2.65.169
Cloudflareserves the site
NS
ns4-01.azure-dns.infons2-01.azure-dns.netns3-01.azure-dns.orgns1-01.azure-dns.com
azure-dns.info + azure-dns.net + moreanswers its DNS
MX
quest-com.i-v1.mx.microsoft
Microsoft 365receives its email

HTTPS probe

redirect Redirecting (3xx) 301 → https://www.quest.com
HTTP status301
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time198 ms
DNS resolutionNOERROR
Redirect chain
https://www.quest.com

Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".

DNS Records

A 2

  • 99.83.129.68
  • 75.2.65.169

MX 1

  • 0quest-com.i-v1.mx.microsoft

TXT 27

  • miro-verification=5d9131a78d085d18a6710c8fb81e005b250bb987
  • anthropic-domain-verification-wfqyw9=kJxuUZmtksHQH645DIsVxNxJQ
  • 00D30000000n44B=1TBRP00000000Kz
  • MS=ms24973657
  • vmware-cloud-verification-b6bf47ce-f002-4a8d-bd85-29dbc3d16a72
  • google-site-verification=T3xISVl4koljlaH-7F9aM0EW1WHsrV9Mv1sWfwjm2TE
  • adobe-idp-site-verification=ab978135-83ba-47c6-9b83-cc5dd594891d
  • atlassian-domain-verification=kAToQLOqhUe7w6O9HFIf2Dc/d6Em3H4ZvoF8n40E0R3BaJD0IwEoTWKBEGNKSLVB
  • pardot1099863=bf67df324b4d2138872655f1ae668fcac12835f28a3f1c10177e6c7a0df937b9
  • bw=zNbbfMSfQSrPPWB2virgyKy9OFW4tMqi5ZH5hsP2nJf2

NS 4

  • ns4-01.azure-dns.info
  • ns2-01.azure-dns.net
  • ns3-01.azure-dns.org
  • ns1-01.azure-dns.com

SOA 1

  • ns1-01.azure-dns.com azuredns-hostmaster.microsoft.com

TLS Certificates (0)

None.

Subdomains (18)

The proof

Signed at scan time. Check the math yourself. Every line above is part of one signed observation. Re-hash it and check the Ed25519 signature in your own browser; nothing leaves your machine.

Verify this receipt

Put the receipt on your own site. A live badge showing what DomainDrift observes and signs for quest.com. It updates itself. It attests a signed observation - not that the site is safe.

DomainDrift signed-observation badge for quest.com <a href="https://domaindrift.io/t/quest.com"> <img src="https://domaindrift.io/badge/quest.com.svg" width="300" height="64" alt="DomainDrift signed observations for quest.com"> </a>

Ed25519 Receipt

Receipt ID
ee4a8896-22da-459e-91d0-7ed583c9d51d
Output Hash
802dd59c6373a5a560b14c5a162fe3c0a9c3fe214c4d06bb51abaa25a68af04b
Signature
ed25519:4da05e9c50296d17f23d20a6942082d3f47811135ae0c12ea0ece8952fb7a14b1c5562d65e4249976e9f7a92b374bc00c20dcec31f7b003e802f752cf415e904
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser