May we count visits with Google Analytics? It sets cookies and sends usage data to Google. Nothing loads unless you allow it. Cookie details
campaign-attribution-gateway.stage.api.bbc.co.uk DNS Records: A, MX, NS, TXT | OrbitProbe
campaign-attribution-gateway.stage.api.bbc.co.ukObserved: Oct 12, 2026, 03:00 AM UTCPage: https://www.orbitprobe.com/dns-lookup/campaign-attribution-gateway.stage.api.bbc.co.uk
DNS records for campaign-attribution-gateway.stage.api.bbc.co.uk
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
Some query types failed and may be missing: SOA. A missing record here is not evidence of absence. [EBADRESP]
The tool asks public recursive resolvers for the record types that matter in day-to-day operations: A and AAAA for IPv4 and IPv6 addresses, NS for the authoritative nameservers, MX for mail routing, TXT for SPF, domain verification and similar data, CAA for certificate authority restrictions, SOA for zone metadata and CNAME for aliases.
Each answer is shown with its TTL and the resolver that returned it. If a record type does not exist, the result says so explicitly, because the absence of a record is often the answer you were looking for.
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.
19 checks since Sep 26, 2026, the latest on Oct 10, 2026.
Changes observed
IPv4 addresses (A) changed on Oct 10, 2026 ()Before: 40.180.60.78, 54.155.113.11After: 54.155.113.11, 79.125.112.165Source: DNS · public resolvers 1.1.1.1, 8.8.8.8
IPv4 addresses (A) changed on Oct 9, 2026 ()Before: 40.180.60.78, 52.16.249.69After: 40.180.60.78, 54.155.113.11Source: DNS · public resolvers 1.1.1.1, 8.8.8.8
IPv4 addresses (A) changed on Oct 4, 2026 ()Before: 52.210.116.148, 52.210.176.184After: 40.180.60.78, 52.16.249.69Source: DNS · public resolvers 1.1.1.1, 8.8.8.8
IPv4 addresses (A) changed on Sep 29, 2026 ()Before: 52.210.116.148, 54.216.199.255After: 52.210.116.148, 52.210.176.184Source: DNS · public resolvers 1.1.1.1, 8.8.8.8
Values on record
IPv4 addresses (A)
54.155.113.11, 79.125.112.165
5 distinct values so far · unchanged since Oct 10, 2026, seen in 2 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.
How this domain compares
Fixed points of reference, not rankings. Each line says what the value is compared with and where it came from.
IPv4 only: 2 A records and no AAAA record at this name.Source: DNS · public resolvers 1.1.1.1, 8.8.8.8 · Observed:
