saravanabhavan.com
Observed Aug 16, 2026, 06:49 UTC (1d ago). Every field below was attested with an Ed25519 signature at scan time.
saravanabhavan.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting saravanabhavan.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 saravanabhavan.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Google Trust ServicesSteady. No change on record for saravanabhavan.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
199.36.158.100
MX 2
20mx-biz.mail.am0.yahoodns.net30mx-biz.mail.am0.yahoodns.net
TXT 1
hosting-site=saravanabhavan-global-website
NS 2
ns1.turbify.comns2.turbify.com
SOA 1
ns1.turbify.com webmaster.turbify.com
MCP_RECORDS 1
v=spf1 a mx ip4:40.90.252.187 include:relay.mailchannels.net -all
DMARC_RECORDS 1
v=spf1 a mx ip4:40.90.252.187 include:relay.mailchannels.net -all
BIMI_RECORDS 1
v=spf1 a mx ip4:40.90.252.187 include:relay.mailchannels.net -all
MTA_STS_RECORDS 1
v=spf1 a mx ip4:40.90.252.187 include:relay.mailchannels.net -all
TLS Certificates (4)
| Common Name | Issuer | Expires |
|---|---|---|
saravanabhavan.ae |
C=US, O=Google Trust Services, CN=WR3 | Sun, 11 Oct 2026 12:06:51 +0000 |
WR3 |
C=US, O=Google Trust Services LLC, CN=GTS Root R1 | Tue, 20 Feb 2029 14:00:00 +0000 |
GTS Root R1 |
C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA | Fri, 28 Jan 2028 00:00:42 +0000 |
GlobalSign Root CA |
C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA | Fri, 28 Jan 2028 12:00:00 +0000 |
Subdomains (2)
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_2c6a55dd355b56c5- Output Hash
4a16507751beb8a3889ef79afdc59ab985000243987e35f1df2de1f7388a7122- Signature
ed25519:f0a8cfd2a4cd4c566e6f8bd7e85de40d5978ed113105233f361cd44294a8c2fa5243ec0cd136f0fb24025a3a272d650516392f91ebb35c163d7ad9ffbca51f06- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast