bitcongress.com

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

This reading of bitcongress.com was taken 4d ago

bitcongress.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting bitcongress.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 bitcongress.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onCloudflare
Secured byGoogle Trust Services
Registered withAlibaba Cloud Computing (Beijing) Co., Ltd.
IPv6 · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat bitcongress.com actually stands on - every host below is a signed observation
bitcongress.com
A / AAAA
104.21.2.153172.67.129.872606:4700:3030::6815:2992606:4700:3035::ac43:8157
Cloudflareserves the site
NS
arch.ns.cloudflare.comkira.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
mxcom.263xmail.commxwcom.263xmail.com
263xmail.comreceives its email
TLS
bitcongress.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 104.21.2.153
  • 172.67.129.87

AAAA 2

  • 2606:4700:3030::6815:299
  • 2606:4700:3035::ac43:8157

MX 2

  • 10mxcom.263xmail.com
  • 5mxwcom.263xmail.com

TXT 1

  • v=spf1 include:spf.263xmail.com ~all

NS 2

  • arch.ns.cloudflare.com
  • kira.ns.cloudflare.com

SOA 1

  • arch.ns.cloudflare.com dns.cloudflare.com

TLS Certificates (3)

Common NameIssuerExpires
bitcongress.com C=US, O=Google Trust Services, CN=WE1 Sat, 07 Nov 2026 14:25:13 +0000
WE1 C=US, O=Google Trust Services LLC, CN=GTS Root R4 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R4 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 (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_a3977d4b3d33282f
Output Hash
785a807ad6ca03ae7a71de147cc87179b438cfd9615aa3d7a304e24b02883ff2
Signature
ed25519:df04aad57dbcf9562607f7c88766284242100b9926d28db9f604124e735e6e0a883b85ad4fceadc1c0d810153464cd8845ab410366af7b336215cc578f6c9809
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT47,821 material changesacross 45,734 domains · 24h to ~85m ago · +1,951 vs yesterdayROTATION60 domains moved DNS from koaladns.com to magpiedns.com, 59 moved backa rotation loop, not a migration · 24hCERT DRIFT1 domains switched issuing CA24hREGISTRAR DRIFT2 changed registrar24hNOW494 curated domains not reachablelast probe, steadySITE ERRORS36,461 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 115,878 sites429 rate-limit / 403 bot-block, a posture signal