CONTINUOUS INTERNET TELEMETRY24H DRIFT3,030 material changesacross 2,719 domains · -368 vs yesterdayDNS DRIFT24 domains changed DNS providertop destination cloudflare.com · -3 vs yesterdayEMAIL DRIFT3 domains switched email providertop destination h-email.net · -3 vs yesterdayCERT DRIFT8 domains switched issuing CA24h · +1 vs yesterdayNOW3,311 curated domains not answering-6,407 vs yesterdayERRORS10,953 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT3,030 material changesacross 2,719 domains · -368 vs yesterdayDNS DRIFT24 domains changed DNS providertop destination cloudflare.com · -3 vs yesterdayEMAIL DRIFT3 domains switched email providertop destination h-email.net · -3 vs yesterdayCERT DRIFT8 domains switched issuing CA24h · +1 vs yesterdayNOW3,311 curated domains not answering-6,407 vs yesterdayERRORS10,953 responded with an errorlast probe · 5xx / 404 / 429 / 403

ctrls.in

Observed 2026-07-12T21:42:00.104Z (15h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Also usesAtlassianGoogle Search Console
6 subdomains · tranco_5k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat ctrls.in actually stands on - every host below is a signed observation
ctrls.in
A / AAAA
154.210.173.167
Cloudflareserves the site
NS
ns2.ctrls.inns1.ctrls.inns20.ctrls.in
ctrls.inanswers its DNS
MX
mx2.hc1097-55.ap.iphmx.commx1.hc1097-55.ap.iphmx.com
iphmx.comreceives its email

HTTPS probe

redirect Redirecting (3xx) 302 → https://www.ctrls.in/
HTTP status302
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time1570 ms
DNS resolutionNOERROR
Redirect chain
https://www.ctrls.in/

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

DNS Records

A 1

  • 154.210.173.167

MX 2

  • 5mx2.hc1097-55.ap.iphmx.com
  • 5mx1.hc1097-55.ap.iphmx.com

TXT 16

  • globalsign-domain-verification=aQLAddNOettg5NSWEmzxVigcm87d16svUPK0OFwbbP
  • MS=ms69503099
  • atlassian-domain-verification=MwI21KYuB9H5jds4NmprUCbF9nv9fozfT1ISsi5IPpnZAkWJu5lTOqJwTcawFa7U
  • google-site-verification=LHdokmWZLCWkNM6jWI28tf8_Eak7mZzri1eKtEj6FNk
  • google-site-verification=4ez-o0cVqdFQNcwew3YL48aYQh2VfQ5I5QLtIFVa7ek
  • zoho-verification=zb79855442.zmverify.zoho.com
  • _globalsign-domain-verification=-mhpQu-oGmDX87UoSMvW1KF9XZfXjRJCkbhLWzSkJc
  • atlassian-sending-domain-verification=6423707f-6b8a-4efc-8cf5-ed22553b3aa5
  • v=spf1 include:_spf_cnt0._ctrls.in._spf.godmarc.io ~all
  • _globalsign-domain-verification=rNlCT9R8_6x3SS5yBr_hhJfUmpL2bYzLTpt6vYQ-Fc

NS 3

  • ns2.ctrls.in
  • ns1.ctrls.in
  • ns20.ctrls.in

SOA 1

  • ns20.ctrls.in hostmaster.ctrls.in

TLS Certificates (0)

None.

Subdomains (6)

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

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

Ed25519 Receipt

Receipt ID
cc377e5a-f5d9-4832-8a85-dfcdc0639891
Output Hash
6fba05a2eb520041124cb44bac906d4f2eea84f875fb408ff2a4e6774ecde627
Signature
ed25519:d5a1350bb7c89f7755ec35aec93b4f8cdde5a20fec1a424775f04ea0ad1e99d3124c9b27ef70496d94ea7e754329a5fe782d2eac748ba0a8a6cbaca89a5deb0b
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser