bf-sinara.com

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

This reading of bf-sinara.com was taken 13d ago

bf-sinara.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting bf-sinara.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 bf-sinara.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onJSC _TIMEWEB_
Secured byLet's Encrypt
Registered withRegional Network Information Center, JSC dba RU-CENTER
DNSSEC on · 2 subdomains · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-15 07:22 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 bf-sinara.com actually stands on - every host below is a signed observation
bf-sinara.com
A / AAAA
78.40.218.130
JSC _TIMEWEB_serves the site
NS
ns1.timeweb.runs4.timeweb.orgns3.timeweb.orgns2.timeweb.ru
timeweb.ru + timeweb.organswers its DNS
MX
mx1.timeweb.rumx2.timeweb.ru
timeweb.rureceives its email
TLS
www.bf-sinara.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 78.40.218.130

MX 2

  • 10mx1.timeweb.ru
  • 10mx2.timeweb.ru

TXT 2

  • yandex-verification: 692dadef7dd66f86
  • v=spf1 include:_spf.timeweb.ru ~all

NS 4

  • ns1.timeweb.ru
  • ns4.timeweb.org
  • ns3.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=spf1 include:_spf.timeweb.ru ~all

BIMI_RECORDS 1

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

MTA_STS_RECORDS 1

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

TLS Certificates (2)

Common NameIssuerExpires
www.bf-sinara.com C=US, O=Let's Encrypt, CN=R13 Wed, 26 Aug 2026 07:19:01 +0000
R13 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Fri, 12 Mar 2027 23:59:59 +0000

Subdomains (2)

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_906bc2b1b33f0c9f
Output Hash
32f18e07ea0f549bf4f7ae258700fbb82ca9eeafdc5dbda705600e38aea107ab
Signature
ed25519:1e9e196016b39e8625d7331c22d40ef954545899fcb054d3e5edfcb1f0da0548926af21f76a5a5cac3786233ed2271be646687a7cc35564a4cc3fdf658b0590d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT45,328 material changesacross 43,735 domains · 24h to ~2h ago · +1,821 vs yesterdayROTATION55 domains moved DNS from koaladns.com to magpiedns.com, 52 moved backa rotation loop, not a migration · 24hNOW495 curated domains not reachablelast probe, steadySITE ERRORS36,285 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,343 sites429 rate-limit / 403 bot-block, a posture signal