DOMAIN RECORD
myengineeringteam.com
- First observed
- 2026-08-17T10:47:20.507Z
- Last observed
- 2026-08-18T14:51:08.790Z
- 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-17T10:45:15.482Z — 1 observation and 1 change event recorded since.
OBSERVATION RAIL
- 2026-08-17T10:47:20.507ZMonitoring from 2026-08-17T10:47:20.507ZNo 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=YR1
- Validity
- 2026-08-17T08:04:15Z → 2026-11-15T08:04:14Z
- First observed
- 2026-08-18T14:51:08.790Z
- Last observed
- 2026-08-18T14:51:08.790Z
- Source
- OMSHIFT CT Monitor (forward observation)
SAN NAMES (2)
myengineeringteam.com, www.myengineeringteam.com
View certificate evidence →FORWARD OBSERVATION
- Issuer
- C=US, O=Let's Encrypt, CN=YR2
- Validity
- 2026-08-17T09:45:43Z → 2026-11-15T09:45:42Z
- First observed
- 2026-08-17T10:47:20.507Z
- Last observed
- 2026-08-17T11:52:34.159Z
- Source
- OMSHIFT CT Monitor (forward observation)
SAN NAMES (2)
myengineeringteam.com, www.myengineeringteam.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.