biznet-us.com

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

This reading of biznet-us.com was taken 3d ago

biznet-us.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting biznet-us.com 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 biznet-us.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onCitytelecom
Secured byLet's Encrypt
Registered withPDR Ltd. d/b/a PublicDomainRegistry.com
DNSSEC on · 54 subdomains · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-13 01:25 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 biznet-us.com actually stands on - every host below is a signed observation
biznet-us.com
A / AAAA
185.229.9.161
Citytelecomserves the site
NS
ns3.timeweb.orgns1.timeweb.runs4.timeweb.orgns2.timeweb.ru
timeweb.org + timeweb.ruanswers its DNS
MX
mx.yandex.net
yandex.netreceives its email
TLS
biznet-us.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 185.229.9.161

MX 1

  • 10mx.yandex.net

TXT 2

  • yandex-verification: e2d3dc77f49fa0cd
  • v=spf1 +a +mx -all

NS 4

  • ns3.timeweb.org
  • ns1.timeweb.ru
  • ns4.timeweb.org
  • ns2.timeweb.ru

SOA 1

  • ns1.timeweb.ru dns.timeweb.ru

MCP_RECORDS 1

  • v=spf1 include:_spf.timeweb.ru ~all

DMARC_RECORDS 1

  • v=DMARC1; p=none

BIMI_RECORDS 1

  • v=spf1 include:_spf.timeweb.ru ~all

MTA_STS_RECORDS 1

  • v=spf1 include:_spf.timeweb.ru ~all

TLS Certificates (3)

Common NameIssuerExpires
biznet-us.com C=US, O=Let's Encrypt, CN=YR1 Sun, 25 Oct 2026 04:20:14 +0000
YR1 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (54)

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_671093137a36c354
Output Hash
b1e1f036d9ac18f3b55b37de29efaeb52bc823a6132632a722c581ab7af32516
Signature
ed25519:67fd87b3ed7838b0b27ca78b8f364e865f39bf04ec78783687400b65377d47aeb6dfe2450f64626316f37171847d9fdd17b706979848e5ff0c32b968978e540d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT45,898 material changesacross 43,837 domains · 24h to ~2h ago · +28 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW490 curated domains not reachablelast probe, steadySITE ERRORS36,284 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 115,595 sites429 rate-limit / 403 bot-block, a posture signal