blog.bg

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

This reading of blog.bg was taken 6d ago

blog.bg is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting blog.bg 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 blog.bg Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onEvolink EAD
Secured byLet's Encrypt
Also usesGoogle 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-14 17:08 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 blog.bg actually stands on - every host below is a signed observation
blog.bg
A / AAAA
85.14.4.125
Evolink EADserves the site
NS
ns5.gotobg.netns6.gotobg.net
gotobg.netanswers its DNS
MX
blog.bg
blog.bgreceives its email
TLS
*.blog.bg
Let's Encryptissued its certificate

DNS Records

A 1

  • 85.14.4.125

MX 1

  • 0blog.bg

TXT 2

  • google-site-verification=gc9z68N0aA0SBWTeTTnnSso6pfroMUYaRVcZAHdowWQ
  • v=spf1 ip4:78.142.47.253 +a +mx +ip4:78.128.76.161 +ip4:79.124.76.10 +ip4:173.237.189.29 +ip4:194.12.227.222/32 +ip4:194.12.229.224/28 +ip4:85.14.4.112/28 +ip4:85.14.21.145/28 +ip4:194.12.229.96/27 ~all

NS 2

  • ns5.gotobg.net
  • ns6.gotobg.net

SOA 1

  • ns5.gotobg.net noc.ns1.bg

MCP_RECORDS 2

  • google-site-verification=gc9z68N0aA0SBWTeTTnnSso6pfroMUYaRVcZAHdowWQ
  • v=spf1 ip4:78.142.47.253 +a +mx +ip4:78.128.76.161 +ip4:79.124.76.10 +ip4:173.237.189.29 +ip4:194.12.227.222/32 +ip4:194.12.229.224/28 +ip4:85.14.4.112/28 +ip4:85.14.21.145/28 +ip4:194.12.229.96/27 ~all

DMARC_RECORDS 2

  • google-site-verification=gc9z68N0aA0SBWTeTTnnSso6pfroMUYaRVcZAHdowWQ
  • v=spf1 ip4:78.142.47.253 +a +mx +ip4:78.128.76.161 +ip4:79.124.76.10 +ip4:173.237.189.29 +ip4:194.12.227.222/32 +ip4:194.12.229.224/28 +ip4:85.14.4.112/28 +ip4:85.14.21.145/28 +ip4:194.12.229.96/27 ~all

BIMI_RECORDS 2

  • google-site-verification=gc9z68N0aA0SBWTeTTnnSso6pfroMUYaRVcZAHdowWQ
  • v=spf1 ip4:78.142.47.253 +a +mx +ip4:78.128.76.161 +ip4:79.124.76.10 +ip4:173.237.189.29 +ip4:194.12.227.222/32 +ip4:194.12.229.224/28 +ip4:85.14.4.112/28 +ip4:85.14.21.145/28 +ip4:194.12.229.96/27 ~all

MTA_STS_RECORDS 2

  • google-site-verification=gc9z68N0aA0SBWTeTTnnSso6pfroMUYaRVcZAHdowWQ
  • v=spf1 ip4:78.142.47.253 +a +mx +ip4:78.128.76.161 +ip4:79.124.76.10 +ip4:173.237.189.29 +ip4:194.12.227.222/32 +ip4:194.12.229.224/28 +ip4:85.14.4.112/28 +ip4:85.14.21.145/28 +ip4:194.12.229.96/27 ~all

TLS Certificates (4)

Common NameIssuerExpires
*.blog.bg C=US, O=Let's Encrypt, CN=YE1 Mon, 31 Aug 2026 12:22:25 +0000
YE1 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

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_d98ff2b0bf4a7223
Output Hash
cc397e44ea8dfe56425b5698a5c42f0cd657064d0dbeacf239d7709f110fd076
Signature
ed25519:dc0f0d8ab9012438e40d5cfe0f98cd3a4c01eed19a5bf5108f41ab0b0e73c9075e29d380b2843779022e0fa0eaf3109e1b261a9ced04239cca4b6cda4f84a408
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT37,675 material changesacross 36,284 domains · 24h to ~3h ago · -5,832 vs yesterdayROTATION63 domains moved DNS from magpiedns.com to koaladns.com, 57 moved backa rotation loop, not a migration · 24hNOW495 curated domains not reachablelast probe, steadySITE ERRORS36,308 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,285 sites429 rate-limit / 403 bot-block, a posture signal