awsl.blog

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

This reading of awsl.blog was taken 3d ago

awsl.blog is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting awsl.blog 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 awsl.blog Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onMULTACOM CORPORATION
Secured byLet's Encrypt
Registered withPorkbun, LLC
Also usesGoogle Search ConsoleKeybase
DNSSEC on · IPv6 · 1 subdomain · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-14 02:07 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 awsl.blog actually stands on - every host below is a signed observation
awsl.blog
A / AAAA
113.20.1.722607:f130:0:155::8e14:bff
MULTACOM CORPORATIONserves the site
NS
duke.ns.cloudflare.combrianna.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
in1-smtp.messagingengine.comin2-smtp.messagingengine.com
messagingengine.comreceives its email
TLS
awsl.blog
Let's Encryptissued its certificate

DNS Records

A 1

  • 113.20.1.72

AAAA 1

  • 2607:f130:0:155::8e14:bff

MX 2

  • 10in1-smtp.messagingengine.com
  • 20in2-smtp.messagingengine.com

TXT 4

  • yandex-verification: f73ec4ee55f5d48d
  • v=spf1 include:spf.messagingengine.com ?all
  • google-site-verification=vqLCbwq6q_stAVji93-yrSlBsVnzH5QHb61QjOwGNYQ
  • keybase-site-verification=VMcAV1qqXUQanltdxqwcL5q0OVMScD2lp4JnYTgxQ2E

NS 2

  • duke.ns.cloudflare.com
  • brianna.ns.cloudflare.com

SOA 1

  • brianna.ns.cloudflare.com dns.cloudflare.com

CAA 12

  • iodef "mailto:admin@awsl.blog"
  • issue "comodoca.com"
  • issue "digicert.com; cansignhttpexchanges=yes"
  • issue "letsencrypt.org"
  • issue "pki.goog; cansignhttpexchanges=yes"
  • issue "sectigo.com"
  • issue "ssl.com"
  • issuewild "comodoca.com"
  • issuewild "digicert.com; cansignhttpexchanges=yes"
  • issuewild "letsencrypt.org"

MCP_RECORDS 4

  • yandex-verification: f73ec4ee55f5d48d
  • v=spf1 include:spf.messagingengine.com ?all
  • google-site-verification=vqLCbwq6q_stAVji93-yrSlBsVnzH5QHb61QjOwGNYQ
  • keybase-site-verification=VMcAV1qqXUQanltdxqwcL5q0OVMScD2lp4JnYTgxQ2E

DMARC_RECORDS 1

  • v=DMARC1; p=none; rua=mailto:fe4373539bcd466e99d4d5ff3ac5497c@dmarc-reports.cloudflare.net

BIMI_RECORDS 4

  • yandex-verification: f73ec4ee55f5d48d
  • v=spf1 include:spf.messagingengine.com ?all
  • google-site-verification=vqLCbwq6q_stAVji93-yrSlBsVnzH5QHb61QjOwGNYQ
  • keybase-site-verification=VMcAV1qqXUQanltdxqwcL5q0OVMScD2lp4JnYTgxQ2E

MTA_STS_RECORDS 4

  • yandex-verification: f73ec4ee55f5d48d
  • v=spf1 include:spf.messagingengine.com ?all
  • google-site-verification=vqLCbwq6q_stAVji93-yrSlBsVnzH5QHb61QjOwGNYQ
  • keybase-site-verification=VMcAV1qqXUQanltdxqwcL5q0OVMScD2lp4JnYTgxQ2E

TLS Certificates (4)

Common NameIssuerExpires
awsl.blog C=US, O=Let's Encrypt, CN=YE1 Tue, 03 Nov 2026 17:28:56 +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 (1)

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_4d8d55741aec4988
Output Hash
af3411a4bdc31bdf8cf1f8419b624cf4fee382cb0159fb91790a3a8fd91b63fd
Signature
ed25519:9c1b96fdf362b70976e313abf806c8f1755786cfa6b4d995ec425be598e055d4ba1cd6c63307703c7d0a8cbc6e7bd203ebcf9ec60322c4b7faa0eb9065bcf50c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT44,221 material changesacross 42,267 domains · 24h to ~2h ago · +139 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 55 moved backa rotation loop, not a migration · 24hNOW490 curated domains not reachablelast probe, steadySITE ERRORS36,526 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 115,984 sites429 rate-limit / 403 bot-block, a posture signal