← eMudhra Technologies Limited cases
Bugzilla #1821508 Incident

eMudhra: CRL occasionally unavailable and returns 404 error

RESOLVED FIXED eMudhra Technologies Limited
This summary was auto-generated by AI and revised by me when needed — accuracy improves with each update. Always refer to the official Bugzilla thread as the authoritative source. If you spot an inaccuracy, let me know via the contact form.
AI Summary

This case reports that eMudhra’s CRL for the “emSign ECC Root CA - G3” (http://crl.emsign.com?RootCAG3.crl) occasionally returns an HTTP 404 error. The issue was observed via SSLmate CRL Watch, and eMudhra stated that their team noticed the problem around 06-Mar-2023. eMudhra investigated, added monitoring (including third-party uptime monitoring and continuous replication of CRL downloads from multiple regions), and determined the suspected cause as a CRL delivery service failing to load CRLs randomly. eMudhra applied an update to the CRL delivery service with necessary tests on 10-Mar-2023 and continued monitoring, stating that the problem impacted CRL responses only and not certificate issuance. In later updates, eMudhra reported that the CRL service was functioning normally, that they did not see the issue again in SSLmate CRL Watch, and that they expanded monitoring to all CRL distribution endpoints listed in CCADB. The bug was resolved as FIXED.

Model: gpt-5.4-nano Generated: 2026-06-13 21:23 UTC Revised: 2026-06-16 18:33 UTC Confidence: 0.86 4 comments
Chronology
  1. eMudhra observed intermittent CRL Watch alerts indicating possible CRL delivery problems for some CRL endpoints.
  2. eMudhra applied an update to the CRL delivery service (with tests) based on log observations.
  3. eMudhra expanded monitoring to all CCADB-listed CRL distribution endpoints and reported satisfactory results.
Thread Activity
  1. Mm representative — Reported that the RootCAG3 CRL URL occasionally returns HTTP 404 with a FileNotFoundException-style error response.
  2. Emudhra representative — Acknowledged the bug, described investigation and monitoring steps, and stated an interim update that a CRL delivery service update was applied while monitoring continued.
  3. Emudhra representative — Reported continued monitoring with normal CRL service behavior and no recurrence in SSLmate CRL Watch.
  4. Emudhra representative — Stated they added monitoring for all CCADB-listed CRL distribution endpoints and requested closure of the bug.
Participants
Mm representative Emudhra representative Community commenter
Similar Local Cases
#1999241 RESOLVED Incident Repository Issue Opened 2025-11-10 · Closed 2025-12-24 · 78% similar
eMudhra emSign PKI Services : Delayed Publication of Issuing CA Certificates in CCADB
#2007297 RESOLVED Incident Repository Issue Opened 2025-12-21 · Closed 2026-02-23 · 77% similar
eMudhra emSign PKI Services: CRL URL Mismatch Between CCADB Disclosure and Issued Certificates
#1819105 RESOLVED Incident Opened 2023-02-27 · Closed 2023-09-29 · 67% similar
NETLOCK: Disclosed CRL is expired
#1651026 RESOLVED Certificate Misissuance Incident Remediation Tracking Opened 2020-07-07 · Closed 2023-02-22 · 66% similar
Izenpe: certificate issued to internal domain
#1708516 RESOLVED Incident Opened 2021-04-29 · Closed 2023-02-22 · 66% similar
Google Trust Services: Failure to provide regular and timely incident updates
#1758372 RESOLVED Incident Opened 2022-03-07 · Closed 2023-02-22 · 66% similar
Google Trust Services: Incorrect OCSP response for issued certificate
#1893546 RESOLVED Incident Opened 2024-04-25 · Closed 2024-07-09 · 66% similar
e-commerce monitoring gmbh: failure to follow incident report requirements
#1949203 RESOLVED Incident Opened 2025-02-19 · Closed 2025-04-03 · 66% similar
Actalis: two CAs with the same CRLDP

We use only essential cookies and local browser storage for preferences and security. See our Privacy Policy for details.

Confirm action