CONTINUOUS INTERNET TELEMETRY24H DRIFT47,514 material changesacross 42,637 domains · 24h to ~2h ago · +13,108 vs yesterdayROTATION54 domains moved DNS from magpiedns.com to koaladns.com, 52 moved backa rotation loop, not a migration · 24hNOW613 curated domains not reachablelast probe, steadySITE ERRORS34,190 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,868 sites429 rate-limit / 403 bot-block, a posture signal

aptana.com

Observed Aug 9, 2026, 20:14 UTC (4m 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.

Verify this receipt yourself + Watch this domain
Guarded by a firewall
Runs onFastly
Email byGoogle Workspace
Secured byLet's Encrypt
Registered withSafeNames Ltd.
IPv6 · 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-06 09:17 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 aptana.com actually stands on - every host below is a signed observation
aptana.com
A / AAAA
23.185.0.42620:12a:8000::42620:12a:8001::4
Fastlyserves the site
NS
sec1.rcode0.orgdns2.p06.nsone.netsec2.rcode0.netdns1.p06.nsone.net
rcode0.org + nsone.net + moreanswers its DNS
MX
alt2.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comalt1.aspmx.l.google.com+1 more
Google Workspacereceives its email
TLS
appcelerator.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 23.185.0.4

AAAA 2

  • 2620:12a:8000::4
  • 2620:12a:8001::4

MX 5

  • 5alt2.aspmx.l.google.com
  • 1aspmx.l.google.com
  • 10aspmx2.googlemail.com
  • 5alt1.aspmx.l.google.com
  • 10aspmx3.googlemail.com

NS 4

  • sec1.rcode0.org
  • dns2.p06.nsone.net
  • sec2.rcode0.net
  • dns1.p06.nsone.net

SOA 1

  • aptxdnsext01.axway.net hostmaster.axway.com

TLS Certificates (3)

Common NameIssuerExpires
appcelerator.com C=US, O=Let's Encrypt, CN=YR2 Sat, 26 Sep 2026 11:35:30 +0000
YR2 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR 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_67675e1d0d86c42b
Output Hash
3c137947bea8c5c3872d398058dcf7d23c546e75e34859b5c1b306722d375c72
Signature
ed25519:d63abb7a41bea21a3de5196eee34aa7ee3c7072c8759c642144de4b2b479d982bae881f8415a638efae20c7bbc1818b192a719216a24ee8fbf5e20b6a302ce07
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser