CONTINUOUS INTERNET TELEMETRY24H DRIFT54,366 material changesacross 47,273 domains · last 24h · +19,960 vs yesterdayROTATION53 domains moved DNS from magpiedns.com to koaladns.com, 51 moved backa rotation loop, not a migration · 24hNOW608 curated domains not reachablelast probe, steadySITE ERRORS34,089 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,502 sites429 rate-limit / 403 bot-block, a posture signal

netcore.co.in

Observed Aug 3, 2026, 01:42 UTC (6d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of netcore.co.in was taken 6d ago

netcore.co.in is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting netcore.co.in under watch moves it to the fast lane, where DomainDrift re-checks it about every 5 minutes and signs each reading, so a change becomes a dated event within minutes instead of waiting for the sweep to come round.

Watch netcore.co.in Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Not responding
Signed observation on record.
Also usesAtlassianGoogle Search Console
tranco_100k
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-09 02:54 UTC

DomainDrift asked this domain for a TXT record at a name nobody registers, and got an answer back. A domain that answers a name that was never created is answering names in general, and that is wildcard DNS.

Wildcard DNS clusters around domain parking, dynamic DNS and catch-all hosting. It is also a real attack surface: if every invented hostname resolves, then a hostname an attacker invents resolves too, which is the ground state for subdomain takeover and for phishing hosted under a name that looks legitimate.

This is evidence of wildcard behaviour, not a proven fact. It rests on one control name: a domain could legitimately serve a TXT record at exactly that name for an unrelated reason, and a wildcard that answers address records but not TXT records would not be caught here at all. What this reading is and is not.

INFRASTRUCTURE MAPwhat netcore.co.in actually stands on - every host below is a signed observation
netcore.co.in
A / AAAA
52.76.10.15
unattributedserves the site
NS
ns-1224.awsdns-25.orgns-1930.awsdns-49.co.ukns-428.awsdns-53.comns-831.awsdns-39.net
awsdns-25.org + awsdns-49.co.uk + moreanswers its DNS
MX
cluster3.netcore.co.incluster8.netcore.co.incluster2.netcore.co.incluster6.netcore.co.in
netcore.co.inreceives its email

DNS Records

A 1

  • 52.76.10.15

MX 4

  • 10cluster3.netcore.co.in
  • 20cluster8.netcore.co.in
  • 5cluster2.netcore.co.in
  • 5cluster6.netcore.co.in

TXT 12

  • 00D2v000003PIc1=1TBfw000000021p
  • OneIDP=bfc2946229029f73be0975c0263b8936
  • globalsign-domain-verification=2ai2bancnHoeK05ocBbIjfsN6lFQYthUWGyOZoI5Zy
  • globalsign-domain-verification=SQEyy1bWEKJAmCxgihGY77z1vg5ppbk0ILD5fVh6Lx
  • globalsign-domain-verification=lpJQckbAdUn1X9gcvwe9a2Yog8O-vQjosC2BDeU1Tx
  • google-site-verification=NE9YK_ivlZ4qGormDbqjGTsZgsmzP2SstXX6OHLZX_Q
  • google-site-verification=Sj49qfkAQNDjs54V9o_wVeYIlZvyY-iU3pzL6aROsHg
  • google-site-verification=dYp094FTDHV4T1SAVYlf3iXvluuz0R9PRhZLaOvbTK0
  • google-site-verification=fA1GQ4tz3AxD7n5UcRuS08aICRsm-dUTAlQOt_qvzDA
  • pardot864782=82938ae1de3fc49380314c3e556e389869c63a2d13f46ef5e73c7fe64bf287dc

NS 4

  • ns-1224.awsdns-25.org
  • ns-1930.awsdns-49.co.uk
  • ns-428.awsdns-53.com
  • ns-831.awsdns-39.net

SOA 1

  • ns-1930.awsdns-49.co.uk awsdns-hostmaster.amazon.com

MCP_RECORDS 2

  • google-site-verification=dYp094FTDHV4T1SAVYlf3iXvluuz0R9PRhZLaOvbTK0
  • v=spf1 include:spf1.netcore.co.in include:spf2.netcore.co.in include:spf3.netcore.co.in include:spf4.netcore.co.in include:spf5.netcore.co.in include:spf6.netcore.co.in ~all

DMARC_RECORDS 1

  • v=DMARC1; p=none; sp=none; rua=mailto:dmarc-reports@netcorecloud.com

BIMI_RECORDS 2

  • google-site-verification=dYp094FTDHV4T1SAVYlf3iXvluuz0R9PRhZLaOvbTK0
  • v=spf1 include:spf1.netcore.co.in include:spf2.netcore.co.in include:spf3.netcore.co.in include:spf4.netcore.co.in include:spf5.netcore.co.in include:spf6.netcore.co.in ~all

MTA_STS_RECORDS 2

  • google-site-verification=dYp094FTDHV4T1SAVYlf3iXvluuz0R9PRhZLaOvbTK0
  • v=spf1 include:spf1.netcore.co.in include:spf2.netcore.co.in include:spf3.netcore.co.in include:spf4.netcore.co.in include:spf5.netcore.co.in include:spf6.netcore.co.in ~all

TLS Certificates (0)

None.

Subdomains (0)

None observed.

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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_6814f5aaf3665b37
Output Hash
4105e9c19529da6fb4c2305bfd2c41f03ac655c5b041089a8e125aaccd4f67d1
Signature
ed25519:849f4ea16c941270615268807f6ac198cd4f64855ded07a5d8106f7b0fbf0a05b593f431dec76cfa5e746a11447ad629eabfa534985a83e0f78e7d372cb53504
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser