DOMAIN RECORD
captainsjourney.com
- First observed
- 2026-08-18T05:31:13.046Z
- Last observed
- 2026-08-19T19:49:02.169Z
- 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-18T02:52:59.975Z — 1 observation and 1 change event recorded since.
OBSERVATION RAIL
- 2026-08-18T05:31:13.046ZMonitoring from 2026-08-18T05:31:13.046ZNo 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=YE1
- Validity
- 2026-08-17T19:14:04Z → 2026-11-15T19:14:03Z
- First observed
- 2026-08-19T19:49:02.169Z
- Last observed
- 2026-08-19T19:49:02.169Z
- Source
- OMSHIFT CT Monitor (forward observation)
SAN NAMES (2)
*.captainsjourney.com, captainsjourney.com
View certificate evidence →FORWARD OBSERVATION
- Issuer
- C=US, O=Google Trust Services, CN=WE1
- Validity
- 2026-08-18T01:51:16Z → 2026-11-16T02:51:12Z
- First observed
- 2026-08-18T05:31:13.046Z
- Last observed
- 2026-08-18T05:31:13.046Z
- Source
- OMSHIFT CT Monitor (forward observation)
SAN NAMES (1)
captainsjourney.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.