re.cr
Observed Aug 10, 2026, 22:14 UTC (7d ago). Every field below was attested with an Ed25519 signature at scan time.
re.cr is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting re.cr 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 re.cr Watching a domain needs a DRM3 account. The reading above stays free and public either way.
HubSpot
Let's Encrypt
Facebook/Meta
Google Search ConsoleSteady. No change on record for re.cr 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
162.243.64.59
MX 2
20mx2.emailsrvr.com10mx1.emailsrvr.com
TXT 5
51s79v981j33im043b5gbj2hdrfacebook-domain-verification=rui19jnw1kp50r789zt47szl2fhrc5v=spf1 a mx include:6420318.spf01.hubspotemail.net include:emailsrvr.com ~allbrevo-code:90291f8caf775ca058c4d8722f88b4f9google-site-verification=QK_4qVvKEP5zzRnbLLdYaIQXgSYvHmiOWMPkFoOhb0g
NS 4
b.ns14.netd.ns14.neta.ns14.netc.ns14.net
SOA 1
a.ns14.net admin.propertyshelf.com
MCP_RECORDS 1
v=spf1 a mx ptr include:spf.protection.outlook.com ip4:164.177.165.250 ~all
DMARC_RECORDS 1
v=DMARC1; p=none; pct=100; rua=mailto:re+jnaf1sk1cr8@dmarc.postmarkapp.com; sp=none; aspf=r;
BIMI_RECORDS 1
v=spf1 a mx ptr include:spf.protection.outlook.com ip4:164.177.165.250 ~all
MTA_STS_RECORDS 1
v=spf1 a mx ptr include:spf.protection.outlook.com ip4:164.177.165.250 ~all
TLS Certificates (3)
| Common Name | Issuer | Expires |
|---|---|---|
re.cr |
C=US, O=Let's Encrypt, CN=YR1 | Sun, 08 Nov 2026 03:52:58 +0000 |
YR1 |
C=US, O=ISRG, CN=Root YR | Sat, 02 Sep 2028 23:59:59 +0000 |
Root YR |
C=US, O=Internet Security Research Group, CN=ISRG Root X1 | Thu, 02 Sep 2032 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_aff10f0d0e024062- Output Hash
d26a8b4cb20dac385b86f4db20e42ac6a3f92e871eb7e4c9db8b9017b4618cf9- Signature
ed25519:0d113d03f59963608f8f4657c27ccbd8976deddf2b17b8b58d67045a58ab293838a1f96b9216ccb50a4acea9caae17e332107c79030163a0f0ad018c126e1509- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast