DOMAIN RECORD
leadtimehq.com
- First observed
- 2026-08-21T05:54:14.068Z
- Last observed
- 2026-08-21T10:10:52.333Z
- Observation runs
- 2
- Certificates observed
- 2
- Change events
- 1
MONITORING STARTED
No historical certificate record was available when this domain was admitted. OMSHIFT has been observing public Certificate Transparency logs directly since 2026-08-21T05:23:55.583Z — 1 observation and 1 change event recorded since.
OBSERVATION RAIL
- 2026-08-21T05:54:14.068ZMonitoring from 2026-08-21T05:54:14.068ZNo historical reconstruction — observed only from this point forward.
LATEST CERTIFICATE EVIDENCE
HISTORICAL BOOTSTRAP — historical evidence imported via SSLMate CT Search when this record was established. FORWARD OBSERVATION — observed directly from public CT logs by OMSHIFT.
FORWARD OBSERVATION
- Issuer
- C=US, O=Let's Encrypt, CN=YR2
- Validity
- 2026-06-23T02:54:38Z → 2026-09-21T02:54:37Z
- First observed
- 2026-08-21T09:44:25.929Z
- Last observed
- 2026-08-21T09:44:35.250Z
- Source
- OMSHIFT CT Monitor (forward observation)
SAN NAMES (1)
leadtimehq.com
View certificate evidence →FORWARD OBSERVATION
- Issuer
- C=US, O=Google Trust Services, CN=WE1
- Validity
- 2026-08-21T04:48:17Z → 2026-11-19T05:48:10Z
- First observed
- 2026-08-21T05:54:14.068Z
- Last observed
- 2026-08-21T10:10:52.333Z
- Source
- OMSHIFT CT Monitor (forward observation)
SAN NAMES (2)
*.leadtimehq.com, leadtimehq.com
View certificate evidence →Certificate Transparency observation does not prove a certificate is currently served by this domain, and SAN presence does not prove ownership. See /method for the full trust contract.