CONTINUOUS INTERNET TELEMETRY24H DRIFT1,154 material changesacross 949 domains · -924 vs yesterdayDNS DRIFT3 domains changed DNS providertop destination ac.in · -12 vs yesterdayNOW2,349 curated domains not answering+1,223 vs yesterdayERRORS15,833 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED40,172 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT1,154 material changesacross 949 domains · -924 vs yesterdayDNS DRIFT3 domains changed DNS providertop destination ac.in · -12 vs yesterdayNOW2,349 curated domains not answering+1,223 vs yesterdayERRORS15,833 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED40,172 throttled or blocked our scanner429 rate-limit / 403 bot-block

toronto.com

Observed Jul 19, 2026, 14:54 UTC (2h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Email byMimecast
Also usesFacebook/MetaGoogle Search Console
11 subdomains · tranco_100k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat toronto.com actually stands on - every host below is a signed observation
toronto.com
A / AAAA
192.104.183.209192.104.183.109
Cloudflareserves the site
NS
ns-1548.awsdns-01.co.ukns-1524.awsdns-62.orgns-380.awsdns-47.comns-690.awsdns-22.net
awsdns-01.co.uk + awsdns-62.org + moreanswers its DNS
MX
ca-smtp-inbound-1.mimecast.comca-smtp-inbound-2.mimecast.com
Mimecastreceives its email

HTTPS probe

redirect Redirecting (3xx) 301 → https://www.toronto.com/
HTTP status301
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time197 ms
DNS resolutionNOERROR
Redirect chain
https://www.toronto.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

  • 192.104.183.209
  • 192.104.183.109

MX 2

  • 10ca-smtp-inbound-1.mimecast.com
  • 10ca-smtp-inbound-2.mimecast.com

TXT 6

  • facebook-domain-verification=bbr65c0fzlrs7uyab7s5p1zzbv50y9
  • 6CjcZ3pQzWtTj4xJrCofLK553FogcAM2Tln0FSJd0mzTR5WzspOl/8p3nRV75fC4gZR/346wUuGqXGOl45pqYQ==
  • google-site-verification=3cDupF8WrCF204biUfWbNNXiEZLMDzg5Cztk_rL0R6c
  • v=spf1 mx ip4:192.206.146.0/23 include:spf.protection.outlook.com ~all
  • MS=ms86315197
  • v=DMARC1; p=none; rua=mailto:6031e5d56c20667@rep.dmarcanalyzer.com; ruf=mailto:6031e5d56c20667@for.dmarcanalyzer.com; fo=1;

NS 4

  • ns-1548.awsdns-01.co.uk
  • ns-1524.awsdns-62.org
  • ns-380.awsdns-47.com
  • ns-690.awsdns-22.net

SOA 1

  • ns-380.awsdns-47.com awsdns-hostmaster.amazon.com

TLS Certificates (0)

None.

Subdomains (11)

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 toronto.com. It updates itself. It attests a signed observation - not that the site is safe.

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

Ed25519 Receipt

Receipt ID
f0d6527c-f5a5-4ae9-b035-35e70788309c
Output Hash
0404119967573bb5848bfbd046561a56780060b67a97c77ee7271e3db1007e79
Signature
ed25519:4a5877161b9fd191804765c2689e2856073b577c8a8c396ca7d480bdeb3bc534c7dcb67750187ac2505e2c9d278523d0bbf4b7103881bdb2d09ed93824339f06
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
Verify this in your browser