servantkeeper.com

Observed Aug 16, 2026, 12:06 UTC (2d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of servantkeeper.com was taken 2d ago

servantkeeper.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting servantkeeper.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 servantkeeper.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onCloudflare
Email byAmazon SES
Secured byGoogle Trust Services
Registered withAmazon Registrar, Inc.
Also uses1PasswordSage IntacctMicrosoft 365AtlassianCursorDocuSignGoogle Search Console
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for servantkeeper.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.

SIGNED-OUT VIEW Provider names, posture and counts are shown. The record values - every DNS answer, each subdomain hostname, raw TXT, IPs, cert names and WHOIS - are the product. Sign in for the full signed record, or use the API with a key.

DNS records 22

A1NS4MX2TXT14SOA1

TLS certificates 3

Issued byGoogle Trust Services, GlobalSign
ExpiresMon, 09 No (82d)
Certificate nameswithheld

Subdomains 0

None observed.

WILDCARD DNSobserved 2026-08-17 12:06 UTC

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

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 receiptthe raw cryptographic proof
Receipt ID
rcpt_1563bee1b447bdab
Output Hash
51aba2189be9a61008669f161e5b96557bdcd0a2ec00136cfa42e6324ca65faf
Signature
ed25519:4e0cb0132a464bc4f8fd9e23563aac83a3e6e401dff4630e08c5891f4fa0e640b5ac6babfe43a58524ce082a18be9c152bc41fcaa8020daf88cca2b59c93110b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
CONTINUOUS INTERNET TELEMETRY24H DRIFT10,724 material changesacross 6,121 domains · 24h to ~40m ago · -30,527 vs yesterdayROTATION75 domains moved DNS from magpiedns.com to kirklanddc.com, 75 moved backa rotation loop, not a migration · 24hNOW14 curated domains not reachable-475 vs yesterdaySITE ERRORS17,709 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 78,943 sites429 rate-limit / 403 bot-block, a posture signal