notifications.dash.staging.cloudflare.comObserved: Oct 11, 2026, 04:12 AM UTCPage: https://www.orbitprobe.com/ns-lookup/notifications.dash.staging.cloudflare.com
Nameservers of notifications.dash.staging.cloudflare.com
Opens the print dialog of your browser. Choose "Save as PDF" as the printer there to get a file: the browser writes it, nothing is uploaded.
Share a snapshot of this report
A live report changes with every lookup, so a shared link to it would not show what you see now. A snapshot stores this report as our server observed it and gives it its own link for 30 days. It holds public lookup data only. Anyone with the link can open it; search engines are asked not to index it.
DNS records
Type
Name
Value
TTL
NS
notifications.dash.staging.cloudflare.com
dorthy.ns.cloudflare.com
—
NS
notifications.dash.staging.cloudflare.com
jay.ns.cloudflare.com
—
Resolver: 1.1.1.1, 8.8.8.8
LiveSource: DNS · public resolvers 1.1.1.1, 8.8.8.8Observed:
Change history
What this service recorded for this name on earlier checks. A check happens only when someone opens a report or calls the API: nothing is scheduled, so gaps between checks are normal.
6 checks since Oct 11, 2026, the latest on Oct 11, 2026.
Changes observed
No change in the recorded values across 6 checks.
Values on record
Nameservers in DNS
dorthy.ns.cloudflare.com, jay.ns.cloudflare.com
unchanged since Oct 11, 2026, seen in 4 checks · Source: DNS · public resolvers 1.1.1.1, 8.8.8.8 · Observed:
IPv4 addresses (A)
104.21.70.141, 172.67.136.50
unchanged since Oct 11, 2026, seen in 4 checks · Source: DNS · public resolvers 1.1.1.1, 8.8.8.8 · Observed:
unchanged since Oct 11, 2026, seen in 4 checks · Source: DNS · public resolvers 1.1.1.1, 8.8.8.8 · Observed:
The history is kept for the domain name only; nothing about who looked it up is stored. Entries not seen again for 400 days are deleted. Changing A, AAAA and hosting values are normal for sites behind load balancers or content delivery networks.
What nameservers do
Nameservers are the servers that hold the DNS records of a domain. When someone looks up your website or sends you mail, their resolver first finds out which nameservers are responsible for your domain and then asks one of them. Whoever runs those nameservers decides what every other record says, which is why the NS set is the first thing to check when DNS behaves unexpectedly.
The NS records usually reveal the DNS provider at a glance: a registrar, a CDN such as Cloudflare, a cloud provider or servers the owner runs.
