CONTINUOUS INTERNET TELEMETRY24H DRIFT2,123 material changesacross 1,919 domains · -428 vs yesterdayDNS DRIFT11 domains changed DNS providertop destination afternic.com · -5 vs yesterdayEMAIL DRIFT6 domains switched email providertop destination google.com · +1 vs yesterdayCERT DRIFT1 domains switched issuing CA24h · -4 vs yesterdayNOW3,397 curated domains not answeringlast probe, steadyERRORS10,894 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT2,123 material changesacross 1,919 domains · -428 vs yesterdayDNS DRIFT11 domains changed DNS providertop destination afternic.com · -5 vs yesterdayEMAIL DRIFT6 domains switched email providertop destination google.com · +1 vs yesterdayCERT DRIFT1 domains switched issuing CA24h · -4 vs yesterdayNOW3,397 curated domains not answeringlast probe, steadyERRORS10,894 responded with an errorlast probe · 5xx / 404 / 429 / 403

telefe.com

Observed 2026-07-14T02:44:58.683Z (11h 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 usesDocuSignAtlassianGoogle Search Console
3 subdomains · push_legacy
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat telefe.com actually stands on - every host below is a signed observation
telefe.com
A / AAAA
9.163.40.246
Cloudflareserves the site
NS
ns3-06.azure-dns.orgns2-06.azure-dns.netns4-06.azure-dns.infons1-06.azure-dns.com
azure-dns.org + azure-dns.net + moreanswers its DNS
MX
telefe-com.mail.protection.outlook.com
Microsoft 365receives its email

HTTPS probe

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

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

DNS Records

A 1

  • 9.163.40.246

MX 1

  • 0telefe-com.mail.protection.outlook.com

TXT 24

  • adobe-sign-verification=aaf43de9f7d89d64e1edf648cc172db8
  • docusign=cc82f000-beda-42c1-83c8-2ebf0da5d906
  • docusign=460efbe6-b893-4bbf-b40e-984c253c2ed0
  • v=spf1 include:spf.protection.outlook.com -all
  • wombat-verification=3KwxVCQV1HEp-aRXRTKKaZ5G0frhk
  • onetrust-domain-verification=c3c32e543cd848b6a09d1168df563e9f
  • atlassian-domain-verification=E+wiTTQbdi+aIBlOe7MvMyDmxBdCed/oDG6hRZquh5QIu+JegSoM3VH8Fof+kOz6
  • MS=ms80747745
  • MS=ms46100116
  • google-site-verification=sX4cqiRaPX7NAmO4Xdg1hNstmpuVuI-XMYPDXJWiNIE

NS 4

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

SOA 1

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

TLS Certificates (0)

None.

Subdomains (3)

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

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

Ed25519 Receipt

Receipt ID
d4007436-c538-49cf-af5b-3b1b54445417
Output Hash
9bef00f0ef284fdc6f48cfbd5c9d0442e6ae46f8106e97a239fb3c3c34b18133
Signature
ed25519:14202bf6564d78c80f6eda8e62f70c2bcc1653ec87117684ba88ccd01678ba8a56713896e2bffd39b5038d4d611c49275404fdafaf49891440e467bf4838640f
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser