metaverseworld247.com

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

This reading of metaverseworld247.com was taken 3d ago

metaverseworld247.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting metaverseworld247.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 metaverseworld247.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Registered tojs
Registered withMegazone Corp., dba HOSTING.KR
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-14 05:13 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 metaverseworld247.com actually stands on - every host below is a signed observation
metaverseworld247.com
A / AAAA
91.195.241.232
unattributedserves the site
NS
sl1.sedo.comsl2.sedo.com
sedo.comanswers its DNS
MX
localhost
localhostreceives its email
TLS
metaverseworld247.com
Sectigo Limitedissued its certificate

DNS Records

A 1

  • 91.195.241.232

MX 1

  • 0localhost

TXT 1

  • v=spf1 -all

NS 2

  • sl1.sedo.com
  • sl2.sedo.com

SOA 1

  • sl1.sedo.com hostmaster.sedo.de

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=spf1 -all

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

TLS Certificates (3)

Common NameIssuerExpires
metaverseworld247.com C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA DV R36 Thu, 27 Aug 2026 23:59:59 +0000
Sectigo Public Server Authentication Root R46 C=US, ST=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust RSA Certification Authority Mon, 18 Jan 2038 23:59:59 +0000
Sectigo Public Server Authentication CA DV R36 C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication Root R46 Fri, 21 Mar 2036 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_532078beea0d9d53
Output Hash
dc006e409a01c45ff5a312178f8b23db6e0a209b1c8141b6bcd49ed494674860
Signature
ed25519:aec752b0ffb4cf8322f0ffd8e0da0f6c2bf695a3134647b1196768d5ce27b54de5248260a916935dc5defc3ab3020347d4249d41d052e825e20209890df3e403
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT47,144 material changesacross 45,217 domains · 24h to ~40m ago · +3,637 vs yesterdayROTATION61 domains moved DNS from koaladns.com to magpiedns.com, 59 moved backa rotation loop, not a migration · 24hNOW495 curated domains not reachablelast probe, steadySITE ERRORS36,383 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,323 sites429 rate-limit / 403 bot-block, a posture signal