L

Public preliminary profile

lucis.co

lucis: public signals observed without founder access.

Preliminary scan — not founder-verified

This profile uses only publicly reachable signals. It does not verify internal settings, source code, data handling, provider accounts, or founder declarations, and it does not qualify for the TrustData Verified badge.

Profile status
Preliminary
Last public scan
Aug 2, 2026
Credentials used
None

Public scan observations

Seven public checks, with explicit limitations.

“Not available” means the signal could not be proven from public access. It is never replaced by a guessed value and does not imply that the underlying practice is absent.

CheckStatusPublic evidenceObserved
Homepage security headersNot availableHomepage security headers could not be evaluated.The homepage returned HTTP 403.Aug 2, 2026
TLS certificatePassThe public TLS endpoint presented a current authorized certificate.
  • Certificate issuer: Google Trust Services / WE1
  • Certificate expiration: 2026-09-09T12:06:41.000Z
  • Negotiated TLS protocol: TLSv1.3
  • Certificate chain authorization: Authorized
Aug 2, 2026
Email DNS recordsFailA publicly testable SPF or DMARC record was absent.
  • SPF record: Not available
  • DMARC policy: Not available
  • Public DKIM selector: Not available
DKIM selectors cannot be enumerated; only these common selectors were tested: google, selector1, selector2, default, k1.
Aug 2, 2026
Conventional public filesNot availableOne or more conventional public files could not be confirmed.Aug 2, 2026
Public GitHub repositoryNot availableNo attributable public GitHub organization repository was confirmed.Not finding a repository does not prove that the company has no public repository.Aug 2, 2026
Client-visible trackers and cookiesNot availableClient-visible trackers could not be evaluated.The homepage returned HTTP 403.Aug 2, 2026
Privacy policy URLNot availableA privacy policy URL could not be evaluated.The homepage returned HTTP 403.Aug 2, 2026
Are you the founder of lucis? Claim this profile and start the full verification.

Full verification remains separate from this scan and starts with the existing founder flow.

Claim this profile