DOMAIN RECORD
ftrr2.myds.me
- First observed
- 2026-08-18T19:57:57.781Z
- Last observed
- 2026-08-18T19:58:28.945Z
- 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-18T19:54:19.923Z — 1 observation and 1 change event recorded since.
OBSERVATION RAIL
- 2026-08-18T19:57:57.781ZMonitoring from 2026-08-18T19:57:57.781ZNo 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-18T18:54:26Z → 2026-11-16T18:54:25Z
- First observed
- 2026-08-18T19:57:57.781Z
- Last observed
- 2026-08-18T19:58:28.945Z
- Source
- OMSHIFT CT Monitor (forward observation)
SAN NAMES (1)
ftrr2.myds.me
View certificate evidence →FORWARD OBSERVATION
- Issuer
- C=US, O=Let's Encrypt, CN=YR1
- Validity
- 2026-08-18T18:54:23Z → 2026-11-16T18:54:22Z
- First observed
- 2026-08-18T19:57:54.776Z
- Last observed
- 2026-08-18T19:58:26.481Z
- Source
- OMSHIFT CT Monitor (forward observation)
SAN NAMES (1)
ftrr2.myds.me
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.