bikecalculator.com
Observed Aug 11, 2026, 06:46 UTC (6d ago). Every field below was attested with an Ed25519 signature at scan time.
bikecalculator.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting bikecalculator.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 bikecalculator.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
SectigoSteady. No change on record for bikecalculator.com in the last day; this reading matches the one before it. The steady record is signed like every other reading. Watch it to catch the next move the moment it lands.
DNS Records
A 1
64.29.151.221
MX 3
110mx3c40.carrierzone.com10mx1c40.carrierzone.com100mx2c40.carrierzone.com
TXT 1
v=spf1 a mx include:spfc40.carrierzone.com ~all
NS 3
ns3.aplus.netns2.aplus.netns1.aplus.net
SOA 1
ns1.aplus.net hostmaster.aplus.net
MCP_RECORDS 1
v=spf1 a mx include:spfc40.carrierzone.com ~all
DMARC_RECORDS 1
v=spf1 a mx include:spfc40.carrierzone.com ~all
BIMI_RECORDS 1
v=spf1 a mx include:spfc40.carrierzone.com ~all
MTA_STS_RECORDS 1
v=spf1 a mx include:spfc40.carrierzone.com ~all
TLS Certificates (3)
| Common Name | Issuer | Expires |
|---|---|---|
bikecalculator.com |
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA DV R36 | Sat, 05 Dec 2026 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 |
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 |
Subdomains (1)
DomainDrift asked this domain for one hostname that nobody ever registered, and it answered. A domain that answers invented hostnames is running wildcard DNS. It is common and usually deliberate. A SaaS platform gives every customer a subdomain this way. How the check works
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 receiptEd25519 Receipt
- Receipt ID
rcpt_c21133c0763f6c1e- Output Hash
3f993f56be61a407c26e0725644053b66e2fcb8ddb290ac0be97e76a78358944- Signature
ed25519:0c9ecb91e6cfa26138dfc6fd53ccd794b89ac9ce1b999f250aaf631bb3ce28391f3894e542651727aeced3df67bed74971e5e4362aa2fea0aa9027435785fb09- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast