why3s.com
Observed 2026-07-17T15:36:55.991877501+00:00 (8h ago). Every field below was attested with an Ed25519 signature at scan time.
Not responding
Signed observation on record.
tranco_100k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat why3s.com actually stands on - every host below is a signed observation
why3s.com
A / AAAA
103.138.106.61
unattributedserves the site
NS
ns3.com.why3s.comns1.com.why3s.comns2.com.why3s.com
why3s.comanswers its DNS
MX
why3s.com
why3s.comreceives its email
DNS Records
A 1
103.138.106.61
MX 1
0why3s.com
TXT 1
v=spf1 ip4:103.138.106.61 include:relay01.why3s.com +mx +a ~all
NS 3
ns3.com.why3s.comns1.com.why3s.comns2.com.why3s.com
SOA 1
ns1.com.why3s.com recordsaving.gmail.com
TLS Certificates (0)
None.
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; nothing leaves your machine.
Verify this receiptPut the receipt on your own site. A live badge showing what DomainDrift observes and signs for why3s.com. It updates itself. It attests a signed observation - not that the site is safe.
<a href="https://domaindrift.io/t/why3s.com">
<img src="https://domaindrift.io/badge/why3s.com.svg"
width="300" height="64" alt="DomainDrift signed observations for why3s.com">
</a>
Ed25519 Receipt
- Receipt ID
3986546d-3837-44b4-9379-1deab86bb24e- Output Hash
505dd287057c1ee43b1576d51175bae2e6bf70963ab7ff18b437d7200d789715- Signature
ed25519:c146f394e674c87e5b837d4356169d11bef527b18e6ac9f8d8143f069616dbe43b6ea6844c9f7e832df5e377a8488c8d65289af1ef259d042575521732979f04- Public Key
ed25519:178c3bd0f57d9d64b83cc4630753381e1a465005a2bbba3d032371f24af0bfd8- Parent
(genesis)- Plane
- fast