lamorce.co
Observed Aug 16, 2026, 16:32 UTC (1d ago). Every field below was attested with an Ed25519 signature at scan time.
lamorce.co is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lamorce.co 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 lamorce.co Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Google Trust Services
ZohoSteady. No change on record for lamorce.co 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 2
192.0.78.241192.0.78.182
MX 2
10mx1.titan.email20mx2.titan.email
TXT 2
zoho-verification=zb15298771.zmverify.zoho.comv=spf1 include:zoho.com include:_spf.wpcloud.com include:spf.titan.email ~all
NS 3
ns1.wordpress.comns3.wordpress.comns2.wordpress.com
SOA 1
ns1.wordpress.com hostmaster.wordpress.com
SRV 1
ssl0.ovh.net:465 p0
MCP_RECORDS 2
zoho-verification=zb15298771.zmverify.zoho.comv=spf1 include:zoho.com include:_spf.wpcloud.com include:spf.titan.email ~all
DMARC_RECORDS 1
v=DMARC1;p=none;
BIMI_RECORDS 2
v=spf1 include:zoho.com include:_spf.wpcloud.com include:spf.titan.email ~allzoho-verification=zb15298771.zmverify.zoho.com
MTA_STS_RECORDS 2
v=spf1 include:zoho.com include:_spf.wpcloud.com include:spf.titan.email ~allzoho-verification=zb15298771.zmverify.zoho.com
TLS Certificates (3)
| Common Name | Issuer | Expires |
|---|---|---|
tls.automattic.com |
C=US, O=Google Trust Services, CN=WR1 | Mon, 21 Sep 2026 02:51:48 +0000 |
WR1 |
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 |
Subdomains (0)
None observed.
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_39c375e0bdd35961- Output Hash
d4de5c4ca7575c88ba479609da6ed9bd06751571a99e42cfbd19bd81d86eb929- Signature
ed25519:16beed8830d17c77fd2b56d1e57ec354d5308e02faf4dbab6730ce77802ca9c8152206f019e0a20f935f9b3c68238de35f79fc898f684e7c06de931ac3f1bc02- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast