s-cruises.com
Observed Aug 11, 2026, 00:17 UTC (5d ago). Every field below was attested with an Ed25519 signature at scan time.
s-cruises.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting s-cruises.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 s-cruises.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Let's EncryptDomainDrift asked this domain for a TXT record at a name nobody registers, and got an answer back. A domain that answers a name that was never created is answering names in general, and that is wildcard DNS.
Wildcard DNS clusters around domain parking, dynamic DNS and catch-all hosting. It is also a real attack surface: if every invented hostname resolves, then a hostname an attacker invents resolves too, which is the ground state for subdomain takeover and for phishing hosted under a name that looks legitimate.
This is evidence of wildcard behaviour, not a proven fact. It rests on one control name: a domain could legitimately serve a TXT record at exactly that name for an unrelated reason, and a wildcard that answers address records but not TXT records would not be caught here at all. What this reading is and is not.
DNS Records
A 1
158.160.162.54
MX 1
10mx.yandex.net
TXT 3
yandex-verification: ace00baaea49c61cv=spf1 include:_spf.timeweb.ru include:spf.mindbox.ru include:_spf.yandex.net include:rsndr.ru ~allzbn1dx761rkz22mn55951xm1c3vss640
NS 4
ns2.timeweb.runs1.timeweb.runs4.timeweb.orgns3.timeweb.org
SOA 1
ns1.timeweb.ru dns.timeweb.ru
MCP_RECORDS 1
v=spf1 ip4:176.57.223.0/24 ip4:92.53.116.0/22 ip4:92.53.96.0/22 ip4:92.53.112.0/22 ip4:92.53.104.0/22 ip6:2a03:6f00::/32 include:_spf.yandex.net ~all
DMARC_RECORDS 1
v=DMARC1; p=none; rua=mailto:postmaster@mx1.rusender-mail.ru
BIMI_RECORDS 1
v=spf1 ip4:176.57.223.0/24 ip4:92.53.116.0/22 ip4:92.53.96.0/22 ip4:92.53.112.0/22 ip4:92.53.104.0/22 ip6:2a03:6f00::/32 include:_spf.yandex.net ~all
MTA_STS_RECORDS 1
v=spf1 ip4:176.57.223.0/24 ip4:92.53.116.0/22 ip4:92.53.96.0/22 ip4:92.53.112.0/22 ip4:92.53.104.0/22 ip6:2a03:6f00::/32 include:_spf.yandex.net ~all
TLS Certificates (4)
| Common Name | Issuer | Expires |
|---|---|---|
s-cruises.com |
C=US, O=Let's Encrypt, CN=YE2 | Tue, 27 Oct 2026 13:17:45 +0000 |
YE2 |
C=US, O=ISRG, CN=Root YE | Sat, 02 Sep 2028 23:59:59 +0000 |
Root YE |
C=US, O=Internet Security Research Group, CN=ISRG Root X2 | Thu, 02 Sep 2032 23:59:59 +0000 |
ISRG Root X2 |
C=US, O=Internet Security Research Group, CN=ISRG Root X1 | Thu, 02 Sep 2032 23:59:59 +0000 |
Subdomains (1)
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_7f102e50d6e454b3- Output Hash
c7faa75367eab6856e988c16b4b2c6d7420007f308f8da424019dc240323218a- Signature
ed25519:707b545e7c8d6254df94ca9b9a7cd9cecaca03c34715fc00f96fe7d75824391cfdf876c6ff0e6c1ee836199eef4920026a53d87d1d172d65b3febd7a574aef09- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast