CONTINUOUS INTERNET TELEMETRY24H DRIFT13,565 material changesacross 13,085 domains · 24h to ~70m ago · -27,295 vs yesterdayNOW559 curated domains not reachablelast probe, steadySITE ERRORS34,154 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,321 sites429 rate-limit / 403 bot-block, a posture signal

vaguevisages.com

Observed Aug 2, 2026, 09:15 UTC (10h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.

Up right now
Email byMicrosoft 365
Secured byGoogle Trust Services
1 subdomain · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 09:15 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 vaguevisages.com actually stands on - every host below is a signed observation
vaguevisages.com
A / AAAA
192.0.78.191192.0.78.222
unattributedserves the site
NS
ns2.wordpress.comns3.wordpress.comns1.wordpress.com
wordpress.comanswers its DNS
MX
vaguevisages-com.mail.protection.outlook.com
Microsoft 365receives its email
TLS
tls.automattic.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 192.0.78.191
  • 192.0.78.222

MX 1

  • 0vaguevisages-com.mail.protection.outlook.com

TXT 2

  • v=spf1 include:_spf.wpcloud.com ~all
  • MS=ms70769295

NS 3

  • ns2.wordpress.com
  • ns3.wordpress.com
  • ns1.wordpress.com

SOA 1

  • ns1.wordpress.com hostmaster.wordpress.com

MCP_RECORDS 2

  • v=spf1 include:_spf.wpcloud.com ~all
  • MS=ms70769295

DMARC_RECORDS 1

  • v=DMARC1;p=none;

BIMI_RECORDS 2

  • v=spf1 include:_spf.wpcloud.com ~all
  • MS=ms70769295

MTA_STS_RECORDS 2

  • v=spf1 include:_spf.wpcloud.com ~all
  • MS=ms70769295

TLS Certificates (3)

Common NameIssuerExpires
tls.automattic.com C=US, O=Google Trust Services, CN=WR1 Fri, 11 Sep 2026 21:50:07 +0000
WR1 C=US, O=Google Trust Services LLC, CN=GTS Root R1 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R1 C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA Fri, 28 Jan 2028 00:00:42 +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; nothing leaves your machine.

Verify this receipt

Put the receipt on your own site. A live badge showing what DomainDrift observes and signs for vaguevisages.com. It updates itself. It attests a signed observation - not that the site is safe.

DomainDrift signed-observation badge for vaguevisages.com <a href="https://domaindrift.io/t/vaguevisages.com"> <img src="https://domaindrift.io/badge/vaguevisages.com.svg" width="300" height="64" alt="DomainDrift signed observations for vaguevisages.com"> </a>

Ed25519 Receipt

Receipt ID
rcpt_1083c8dc8c5f37b3
Output Hash
d2bb998c17cbeda2e83793596d34f4f5dd2f6d591b5321918b5ba03e04520707
Signature
ed25519:666014e9073ca79ead7acfeeef96c5b2327e54d53a58ec2d61fa4a5ac5af4ed9dec0ce3c99033d021d37718d99404535591a70b685fe241afd8bd0b9d1a3460e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser