Risorse · 01

Guida OSINT: produrre informazioni affidabili per le decisioni

Un metodo in sei fasi per trasformare fonti aperte sparse in un briefing tracciabile, dettagliato e utilizzabile.

Aggiornato · 14 min

Archivio cyber immaginario senza persone, cassetto nero con lastre di vetro e rete dorata sullo sfondo Illustrazione editoriale generata con IA

Obiettivi di questa guida

  • Interrompere la raccolta di dati senza uno scopo preciso
  • Evitare di confondere la ripetizione con la conferma
  • Rendere visibile l'incertezza
  • Collegare le raccomandazioni alla decisione

Verifica rapida

  • La domanda si può riassumere in una sola frase?
  • È definita la scadenza di validità?
  • Le due fonti sono realmente indipendenti?
  • Le informazioni personali sono necessarie al ragionamento?
  • Il lettore sa cosa potrebbe cambiare la conclusione?

Metodo passo passo

  1. 1

    Inquadrare la decisione

    Indicare la decisione, il suo responsabile, la scadenza e il probabile costo di un errore. Una domanda ben formulata limita l'ambito di applicazione senza imporre la conclusione.

    Risultato: breve documento di una pagina.

  2. 2

    Elaborare un piano di raccolta dati

    Suddividere la domanda in sotto-ipotesi e mappare le fonti che possono confermare, qualificare o confutare ciascuna di esse. Definire una condizione di arresto.

    Risultato: tabella con ipotesi, fonti e stato di avanzamento.

  3. 3

    Tracciare la provenienza

    Conservare l'URL o il riferimento principale, l'autore, la data di pubblicazione, la data di accesso e una copia conforme, ove consentito dalla legge.

    Risultato: registro delle fonti.

  4. 4

    Valutare senza sovrastimare il punteggio

    Valutare separatamente l'affidabilità della fonte e la credibilità delle informazioni. Una fonte attendibile potrebbe avere un interesse; una fonte sconosciuta potrebbe pubblicare un documento autentico.

    Risultato: griglia di confidenza.

  5. 5

    Corroborare e contestare

    Ricercare un'origine indipendente e tentare attivamente di confutare l'ipotesi principale. Diverse riscritture di un documento rimangono un'unica origine.

    Risultato: matrice di corroborazione.

  6. 6

    Rapporto per l'azione

    Iniziare con la risposta breve, quindi con i fatti decisivi, i limiti, gli scenari e l'azione successiva. Conservare i dettagli della raccolta in un'appendice.

    Risultato: documento decisionale e appendici.

Esempio pratico fittizio

Situazione illustrativa

Un team di gestione deve decidere se un segnale pubblico relativo a un partner giustifichi una revisione approfondita. Il team separa il documento originale dalle ripubblicazioni e dai commenti, data ogni elemento e registra ciò che rimane sconosciuto.

Decisione e prove attese

Il brief indica i due fatti che potrebbero influenzare la decisione, il grado di affidabilità di ciascuna conclusione e la data per l'aggiornamento della ricerca.

Indicatori di gestione

IndicatoreCosa misuraPrima azione
CoperturaSottodomande decisionali con almeno una fonte pertinenteIndividuare prospettive non ancora coperte prima di aggiungere fonti simili
IndipendenzaAffermazioni chiave corroborate da origini distinteRisalire a ogni ripetizione fino alla sua fonte primaria
AttualitàEtà delle prove rispetto alla velocità con cui l'argomento cambiaAssegnare una data di scadenza a ciascuna conclusione
TracciabilitàAffermazioni chiave collegate a un riferimento verificabileAggiungere citazioni durante la raccolta

Errori comuni

  • Raccolta prima di formulare la decisione
  • Citare un aggregatore invece della fonte primaria
  • Trasformare la mancanza di prove in prova di assenza
  • Nascondere le contraddizioni per semplificare la conclusione

Domande frequenti

In che modo l'OSINT si differenzia dalla ricerca sul web?

L'OSINT aggiunge un obiettivo definito, un metodo di raccolta, la tracciabilità, la valutazione della fonte e la rendicontazione proporzionata al rischio decisionale.

Quante fonti sono sufficienti?

Non esiste un numero universale. È necessario ricercare fonti indipendenti e una copertura sufficiente delle affermazioni che potrebbero influenzare la decisione.

La raccolta può essere automatizzata?

Sì, per la scoperta, la normalizzazione e il monitoraggio. Ambito, legalità, identità della fonte, contraddizioni e conclusioni richiedono comunque una revisione umana esplicita.

OSINT: origini, riprese e riscontri

OSINT: cinque documenti non sono cinque origini

Il numero di riprese non misura l’indipendenza. Risalite da ciascun documento all’osservazione o acquisizione. Il grafo è fittizio: i collegamenti sono forniti per l’esercizio, non dedotti automaticamente.

Esempio fittizio: riprese e origini
A alimenta B, B alimenta C. D deriva da un’acquisizione distinta; l’origine di E è ignota. Due catene documentate e un’origine irrisolta non danno un verdetto di verità.
OSINT: cinque documenti non sono cinque origini
Documento fittizioCollegamento fornitoLettura prudente
A · Primo sensoreAcquisizione A conservata per l’esercizio.Prima catena; valutare separatamente l’accuratezza del sensore.
B · Articolo che cita AB cita A senza nuova acquisizione.Un’altra ripresa, non un’altra osservazione indipendente.
C · Discussione che cita BC dipende da B e quindi da A.Anche la seconda copia risale ad A.
D · Secondo sensoreAcquisizione D distinta nei dati fittizi.Seconda catena; esaminare la raccolta prima di corroborare.
E · Cattura senza riferimentoOrigine non stabilita nei dati.Non contarla come indipendente né come falsa per difetto.

Cinque documenti, due catene documentate (A e D) e un’origine indeterminata (E). Il conteggio non è un punteggio di credibilità né prova che due osservazioni confermino la stessa affermazione.

Quattro domande prima di concludere

  • Riguardano la stessa affermazione, periodo e oggetto?
  • Le acquisizioni sono distinte o condividono fonte, strumento, errore o distorsione?
  • Quali ipotesi collegano osservazione e conclusione, e cosa le smentirebbe?
  • Quale copia, data di raccolta e collegamento consentono di ripetere il confronto?

ICD 203 tratta qualità delle fonti, incertezza, distinzione tra informazioni e giudizi e analisi delle alternative. Sono riferimenti metodologici per l’esercizio, che non è un prodotto ufficiale né un accreditamento.

ODNI · ICD 203, Analytic Standards · D.6.e(1)–(4) · Fonti consultate il

Aprire l’esploratore C2PA e i casi di pubblicazione →

Indicatori STIX e condivisione TLP

Le note dettagliate di questa edizione sono disponibili in inglese.

Qualify the source before using an indicator

Structured intelligence retains provenance and a version history. For an actionable OSINT note, separate collected facts, the producer’s assertion and the local conclusion, then state what still needs confirmation.

  • Distinguish the declared object creator from the service relaying it.
  • Compare versions, validity window and any revocation before reusing an old indicator.
  • Present producer confidence as a contextual assessment, including its limits and available independent corroboration.

Read the STIX, observations and TLP sharing reference →

Sources checked on · OASIS · STIX 2.1

OSINT: conservare le prove

Le note dettagliate di questa edizione sono disponibili in inglese.

Connect source context, preserved bytes and each handling action

Usable OSINT work retains more than a link and a screenshot. It connects collected material to context, handling roles and transformations used during analysis. The dossier must distinguish observations, technical copies, redacted versions and analytical conclusions.

This editorial method adapts NIST preservation principles for organisational review of sources and files. NIST IR 8387 primarily addresses evidence-management professionals; SP 800-86 covers IT forensics within incident response. Fields and scenarios below are local examples, not a NIST form, certification or guarantee of admissibility.

Archivio vuoto con documenti e supporti per prove digitali Illustrazione editoriale generata con IA
Fictional empty archive with documents, media and secure storage. A conceptual illustration from the collection; it represents neither real evidence nor an agency facility.

Five questions the dossier must keep separate

Five questions the dossier must keep separate
QuestionUseful evidenceLimit to retain
Byte integrityCompare a calculated digest with a protected reference for a specific object and scope.A match identifies neither the author nor the first custodian. A reference rewritten alongside the file no longer protects that comparison.
Origin and contextRecord the claimed source, collection method, useful identifiers and observation conditions.A filename, title or domain visible in an image does not by itself establish provenance.
Custody continuityConnect transfers, receipts, access and actions to identifiable roles and times.An unchanged digest does not fill undocumented periods or transfers.
Transformation and lineageGive an extract, transcription or redacted version a new identifier and retain its parent link.A derivative can have a different digest without being a covert alteration of the preserved object.
Analytical interpretationCite material used, assumptions, alternatives and coverage limits.Intact bytes may contain false, partial or out-of-context information.

Ten proposed preservation-record fields

Ten proposed preservation-record fields
Proposed fieldUseful contentReview check
Identity and scopeCase, object, version, collection type and links to related material.Identify a precise object without conflating a file, whole archive and extract.
Observed sourceURL or system, publication identifier, provider and authorised access context.Separate claimed source, direct observation and material copied by a third party.
Time and clockRaw time, known timezone or offset, collection time and any normalization.Retain clock uncertainty; do not invent ordering between poorly dated events.
Collection methodTool, version, relevant parameters and responsible operator or role.Make the procedure understandable; a logical export is not automatically a complete media image.
Reference digestAlgorithm, value, byte count and exact scope of hashed data.Keep the reference protected against changes made alongside the object.
Location and accessInternal storage reference, access level, owner and useful history.Check who can read, modify, replace or delete both material and its reference record.
Handover and receiptSender, recipient, time, object, purpose and acknowledgement.A declared handover differs from confirmed receipt.
Copies and derivativesParent, new identifier, transformation, tool and digest for each result.Preserve the reference object and state what was removed or transformed.
Preservation incidentsDigest mismatch, unexplained access, missing transfer and handling action.Retain the observed discrepancy; never silently replace the reference to make the check pass.
Purpose and retentionAnalysis purpose, intended recipients, retention policy and review point.Adapt access and retention to the case; the example establishes no universal duration.
Exact copies and derivatives require different comparisons
Exact copies and derivatives require different comparisons E01 is the captured object. E02 is its exact copy with the same bytes and digest. D01 is a redacted derivative of E02 with a new identifier and a different digest. The log connects the objects without conflating their roles. E01 · Captured object Retained reference same bytes E02 · Exact copy Same binary content new object D01 · Redacted derivative Documented new bytes Documented lineage ≠ proof that the source is truthful

Three objects, two binary contents in the exercise

All three objects are invented. Digests below are calculated over their exact UTF-8 strings, with LF after each line including the final line. E01 and E02 have identical content; D01 is documented new content.

Three objects, two binary contents in the exercise
Object / parentScenario roleUTF-8 size and SHA-256
E01Fictional captured object; no parent within this dossier.72 bytes · SHA-256: 26b8f611a7e9a53474ffc21f3e7b7be89ca1bb8cf69f85f526171e9b91eee963
E02 ← E01Exact copy of E01 for technical review.72 bytes · SHA-256: 26b8f611a7e9a53474ffc21f3e7b7be89ca1bb8cf69f85f526171e9b91eee963
D01 ← E02Version of E02 with the textual source replaced by [redacted].51 bytes · SHA-256: 98fd0d2daa0e77e87bfe1f497150a5c8cde80dc5d6b4a14489caacdc54f7f2cc
Inspect the exact strings used to calculate the digests
Inspect the exact strings used to calculate the digests
ObjectJSON string representing the UTF-8 bytes
E01"CASE-TRAINING-07\nstatus=observed\nsource=https://public.example/report/7\n"
E02"CASE-TRAINING-07\nstatus=observed\nsource=https://public.example/report/7\n"
D01"CASE-TRAINING-07\nstatus=observed\nsource=[redacted]\n"

SHA-256 covers text content only here: not the filename, path, permissions or filesystem timestamps. Matching digests therefore do not establish equal metadata, origin or creation time.

Seven records in a fictional chain of custody

All times in this scenario are UTC on 2026-10-22. Roles A–D are fictional. Timestamps express recorded exercise events; they are not qualified timestamp tokens or digital signatures.

Seven records in a fictional chain of custody
UTC time / objectRole and actionRecorded outcome
10:00:00 · E01Collector A: record capture and context.Initial digest and collection reference retained in the scenario.
10:02:00 · E01Custodian B: confirm receipt into preservation storage.Receipt and protected reference recorded; preservation separate from workspace.
10:05:00 · E02Analyst C: create a working copy of E01.Size and digest compared with E01; parent link retained.
10:08:00 · E02Analyst C: declare handover for controlled review.Handover recorded; receipt still pending at this instant.
10:09:00 · E02Reviewer D: acknowledge receipt and check the copy.Receipt linked to the preceding handover; content comparison recorded.
10:15:00 · D01Analyst C: create a redacted derivative of E02.New identifier, transformation and D01 digest recorded; E01 and E02 preserved.
10:20:00 · D01Reviewer D: review the release scope.Redaction review recorded; this example performs no actual publication.

A log does not become tamper-proof because it contains digests. Storage, individual authentication, permissions and reference protection require separate checks. Report a gap explicitly; adding a plausible time afterwards does not repair it.

Eight situations requiring a bounded conclusion

01 · Identical copy, origin still uncorroborated

Fictional observation: E01 and E02 share size and SHA-256; the claimed source of E01 has not been corroborated.

Bounded conclusion: comparison is consistent with a byte-identical copy. It does not prove the claimed author or origin. Next evidence: collection context and independent corroboration.

02 · First digest calculated after a change

Fictional observation: the first available digest was calculated after an edit of unknown extent.

Bounded conclusion: the reference describes the version hashed at that time. It does not establish absence of changes before calculation. Retain this limit and seek a documented earlier copy.

03 · File and reference replaced together

Fictional observation: one account can replace both object and control reference without an independent trail.

Bounded conclusion: a check can become self-consistent after alteration. Preserve protected references and examine rights and logs; comparison alone is insufficient.

04 · Redacted derivative with a new digest

Fictional observation: D01 removes the textual source and has a different digest from E02. The transformation is documented.

Bounded conclusion: this derivative’s difference is expected and must remain visible. Check lineage, removed content and release suitability. A redacted label does not prove absence of residual data.

05 · Digest mismatch on a claimed exact copy

Fictional observation: a claimed exact copy does not match the expected reference digest.

Bounded conclusion: comparison fails for the hashed scope. Isolate the working copy, retain the observation and investigate cause; infer neither malicious intent nor permission to overwrite the reference.

06 · Declared handover without receipt

Fictional observation: a record declares handover at 10:08 but no confirmed receipt is available.

Bounded conclusion: handover is declared; receipt remains unestablished. An unchanged digest does not identify the custodian during the interval. Seek receipt records and disclose the gap.

07 · Unknown timezone in a timeline

Fictional observation: two logs show 10:05 and 10:07, but one clock’s timezone and offset are unknown.

Bounded conclusion: retain raw times and uncertainty; do not infer causality from apparent order. Any normalization must retain an explicit, revisable assumption.

08 · Screenshot with incomplete source coverage

Fictional observation: an intact screenshot shows neither the whole publication nor its display conditions.

Bounded conclusion: it retains an observed view, not necessarily the whole source. Record visible content, missing coverage and possible dynamic versions; distinguish capture fidelity from content truthfulness.

Six checks before handing over an assessment

  • Each important assertion points to an identified object and its collection scope.
  • Digests retain algorithm, exact byte scope and a protected reference.
  • Working copies and derivatives retain parents, versions and transformations.
  • Handover and receipt remain distinct; gaps and uncertain times stay visible.
  • Release uses the intended versions and a review of removed or remaining information.
  • The assessment separates observation, interpretation, assumption and unproven conclusion.

Field numbers, three objects and seven records are a local teaching construction. Document editions and scope are stated so they are not presented as a universal judicial procedure.

Primary sources and method adaptation

Sources reviewed on

PDF: oscuramento e diffusione

Le note dettagliate di questa edizione sono disponibili in inglese.

Redact the assessment without replacing preserved sources

A shareable version and a working reference serve different purposes. Retain lineage and review visible information, hidden content and recipients of the derivative.

  • Give the redacted copy an identifier and retain its parent link.
  • Do not repeat removed values in a widely accessible ticket or screenshot.
  • Test the delivered file, including its text layer and attachments.

See surfaces and the pre-sharing review matrix →

Sources reviewed on · Adobe · Redacting and sanitizing PDFs · Adobe · Redact sensitive content · Adobe · Sanitize PDFs · ICO · Avoid accidental breaches when redacting · ICO · Hidden information in documents · Microsoft · Document Inspector

Cronologie: UTC e fusi orari

Le note dettagliate di questa edizione sono disponibili in inglese.

A displayed date cannot by itself order sources

Collection can encounter repeated local times or receive a publication late. Preserve original text, offset, zone and observation traceability before constructing an OSINT timeline.

  • Seek clarification when one local time has two possible instants.
  • Retain the time-zone rule version used for conversion.
  • Separate computed temporal order, clock quality and causal interpretation.

Read the 12 cases and three dated snapshots →

Sources reviewed on · IETF · RFC 3339 · Python · PEP 495 · Python 3.12 · zoneinfo · IANA · Time Zone Database 2026e · IANA · 2026e Europe rules · OpenTelemetry · Logs Data Model

Riferimenti IANA e interpretazione DNSSEC

Le note dettagliate di questa edizione sono disponibili in inglese.

DNS evidence alone cannot attribute a website

An authenticated DNS response concerns zone data in a trust chain. It does not by itself identify the organisation deciding what content is published.

  • Keep queried name, type, time, resolver and observed response.
  • Separate RDAP registration data, hosting, DNS publication and editorial content.
  • Reconcile independent evidence and preserve unresolved points.

Read the registries and try the cache model →

IETF · RFC 4033 · §3–5 · 2026-10-23

Certificati TLS e intelligence da fonti aperte

Le note dettagliate di questa edizione sono disponibili in inglese.

Certificate Transparency (CT) makes TLS certificates and precertificates observable in public logs. For OSINT and attack-surface research, this is documentary evidence to corroborate: a certificate trace does not establish a live service, current domain control or the identity of a publisher.

Documentary snapshot of Chrome’s list, version 96.3, generated on 7 November 2026 at 13:35:38 UTC and checked on 7 November 2026. Scope: log_list.json only, not every CT log in existence. States and interfaces describe this edition; this page performs no network checks of the logs.

Four different evidence objects

Four different evidence objects
ObjectWhat it helps examineWhat it does not establish alone
Certificate / precertificateDeclared names, issuer, public key and validity period; a precertificate is a distinct object.Server deployment, present DNS resolution or the responsible party’s legal identity.
SCT · Signed Certificate TimestampA log’s signed commitment to incorporate an entry within its MMD.Already demonstrated membership in a tree: a promise is not an inclusion proof.
STH + inclusion proofMembership of a leaf in the root of a tree of a specified size, following cryptographic verification.Consistency of every view of the log or current TLS validity of the certificate.
Consistency proofA relationship between two states of the same tree: the later state extends the earlier one without changing old entries.Worldwide absence of divergent views; observations also need comparison between observers.

IETF · RFC 6962 · Certificate Transparency · June 2013 · Experimental · §§2.1, 3, 5.4, 7

Two interface families in the snapshot

The source’s “logs” entries correspond to RFC 6962; “tiled_logs” entries to static-ct-api. The latter separates submission and static-resource monitoring prefixes while producing SCTs according to RFC 6962. It is not another name for CT v2. RFC 9162 describes version 2.0 and obsoletes RFC 6962 as a document; that does not automatically turn deployed interfaces into v2.

C2SP · Static Certificate Transparency API · v1.1.0

IETF · RFC 9162 · Certificate Transparency Version 2.0 · December 2021 · Experimental · obsoletes RFC 6962

Read the fields without changing their meaning

Read the fields without changing their meaning
Source fieldCorrect readingAnalytical pitfall
log_idSHA-256 of the DER SubjectPublicKeyInfo public key, encoded as base64.A human-readable log name does not replace this cryptographic identifier.
state + timestampThe distributor’s state for the log and the instant it entered that state.That instant is not a certificate’s issuance date.
mmdDeclared maximum merge delay in seconds.It is neither measured uptime nor certificate validity duration.
temporal_intervalAccepted NotAfter expiry dates: inclusive start, exclusive end.It is not the log’s operational lifetime.
url / monitoring_url / submission_urlLog interface prefixes, retaining their respective roles.A static monitoring prefix is not an RFC 6962 get-entries API.

Google Chrome · Log list schema v3 · Schema v3 checked against signed snapshot 96.3 · 2026-11-07

Understand the four states present

Understand the four states present
State at list timeDocumentary interpretation
usableUsable in Chrome’s described lifecycle; this label is not a health measurement performed by CIE.
qualifiedAdmitted following initial monitoring; recognition propagates through client releases.
readonlyThe log stops issuing new SCTs; a final tree size and root are published in the source.
retiredThe log is no longer relied on to create new SCTs. Analysis of old SCTs depends on their dates and the client’s policy, among other factors.

Other states exist, including pending and rejected, but are absent from this snapshot. This table explains labels; it does not calculate a certificate’s compliance with a browser policy.

Google Chrome · CT Log Lifecycle · Consulted 2026-10-23

Explore the 89 logs in the dated list

Filters apply to the local snapshot only. All 89 rows remain available without JavaScript. Global counts retain the complete scope; filtered results have a separate counter. Prefixes are displayed as documentary data without automatic requests. The table has its own vertical and horizontal scrolling region, accessible by keyboard.

Log nell’istantanea
89
Operatori
11
usable
43
readonly
2
qualified
41
retired
3
RFC 6962
26
static-ct-api
63

Log visualizzati : 89 / 89

Explore the 89 logs in the dated list · 2026-11-07T13:35:38Z
Log and LogIDOperatorState at list timeMMD (s)Accepted NotAfter · UTCInterface and prefixes
Google Argon2026h2
Dettagli tecnici

LogID: 1219ENGn9XfCx+lf1wC/+YLJM1pl4dCzAXMXwMjFaXc=

Googleusable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://ct.googleapis.com/logs/us1/argon2026h2/

Google Argon2027h1
Dettagli tecnici

LogID: 1tWNqdAXU/NqSqDHV0kCr+vH3CzTjNn3ZMgMiRkenwI=

Googleusable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://ct.googleapis.com/logs/us1/argon2027h1/

Google Xenon2026h2
Dettagli tecnici

LogID: 2AlVO5RPev/IFhlvlE+Fq7D4/F6HVSYPFdEucrtFSxQ=

Googleusable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://ct.googleapis.com/logs/eu1/xenon2026h2/

Google Xenon2027h1
Dettagli tecnici

LogID: RMK9DOkUDmSlyUoBkwpaobs1lw4A7hEWiWgqHETXtWY=

Googleusable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://ct.googleapis.com/logs/eu1/xenon2027h1/

Google ParcelYard2026h2
Dettagli tecnici

LogID: utuIpG+cr6QJDoLlk1bbbni0pT9YLbCBl5UkLym2jJg=

Googleusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://parcelyard2026h2.prod.certificate.transparency.goog/

monitoring_url: https://storage.googleapis.com/parcelyard2026h2.prod.certificate.transparency.goog/

Google ParcelYard2027h1
Dettagli tecnici

LogID: HIl0B+YBCgEpO7Z439ejaM6xjMpSHcyk04bkoy5bXQQ=

Googleusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://parcelyard2027h1.prod.certificate.transparency.goog/

monitoring_url: https://storage.googleapis.com/parcelyard2027h1.prod.certificate.transparency.goog/

Google ParcelYard2027h2
Dettagli tecnici

LogID: aYS3IzyydLLRRn2l4EDXH+upCiHniGU3Srn5vPhocjc=

Googleusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://parcelyard2027h2.prod.certificate.transparency.goog/

monitoring_url: https://storage.googleapis.com/parcelyard2027h2.prod.certificate.transparency.goog/

Google PlumbersArms2026h2
Dettagli tecnici

LogID: IPBfqqOkkvxqwUjMM6ICNhhrSfqpfmuzkk+yXsNrHDU=

Googleusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://plumbersarms2026h2.prod.certificate.transparency.goog/

monitoring_url: https://storage.googleapis.com/plumbersarms2026h2.prod.certificate.transparency.goog/

Google PlumbersArms2027h1
Dettagli tecnici

LogID: X/nA+6QtrHjOZELrGazggaKb1OL7U68MYzB55QWCBMk=

Googleusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://plumbersarms2027h1.prod.certificate.transparency.goog/

monitoring_url: https://storage.googleapis.com/plumbersarms2027h1.prod.certificate.transparency.goog/

Google PlumbersArms2027h2
Dettagli tecnici

LogID: M3qex8rmqQSLdS8tk65+SyqQLSG0lxKdg+J5x1PJL4w=

Googleusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://plumbersarms2027h2.prod.certificate.transparency.goog/

monitoring_url: https://storage.googleapis.com/plumbersarms2027h2.prod.certificate.transparency.goog/

Cloudflare Nimbus2026
Dettagli tecnici

LogID: yzj3FYl8hKFEX1vB3fvJbvKaWc1HCmkFhbDLFMMUWOc=

Cloudflareusable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://ct.cloudflare.com/logs/nimbus2026/

Cloudflare Nimbus2027
Dettagli tecnici

LogID: TGPcmOWcHauI9h6KPd6uj6tEozd7X5uUw/uhnPzBviY=

Cloudflareusable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://ct.cloudflare.com/logs/nimbus2027/

DigiCert Wyvern2026h2
Dettagli tecnici

LogID: wjF+V0UZo0XufzjespBB68fCIVoiv3/Vta12mtkOUs0=

DigiCertusable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://wyvern.ct.digicert.com/2026h2/

DigiCert Wyvern2027h1
Dettagli tecnici

LogID: ABpdGhwtk3W2SFV4+C9xoa5u7zl9KXyK4xV7yt7hoB4=

DigiCertusable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://wyvern.ct.digicert.com/2027h1/

DigiCert Wyvern2027h2
Dettagli tecnici

LogID: N6oHzCFvLm2RnHCdJNj3MbAPKxR8YhzAkaX6GoTYFt0=

DigiCertusable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://wyvern.ct.digicert.com/2027h2/

DigiCert Sphinx2026h2
Dettagli tecnici

LogID: lE5Dh/rswe+B8xkkJqgYZQHH0184AgE/cmd9VTcuGdg=

DigiCertusable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://sphinx.ct.digicert.com/2026h2/

DigiCert Sphinx2027h1
Dettagli tecnici

LogID: RqI5Z8YNtkaHxm89+ZmUdpOmphEghFfVVefj0KHZtkY=

DigiCertusable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://sphinx.ct.digicert.com/2027h1/

DigiCert Sphinx2027h2
Dettagli tecnici

LogID: H7D4qS2K3aEhd2wF4qouFbrLxitlOTaVV2qqtS4R0R0=

DigiCertusable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://sphinx.ct.digicert.com/2027h2/

Sectigo Mammoth2026h2
Dettagli tecnici

LogID: lLHBirDQV8R74KwEDh8svI3DdXJ7yVHyClJhJoY7pzw=

Sectigoreadonly

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://mammoth2026h2.ct.sectigo.com/

Sectigo Sabre2026h2
Dettagli tecnici

LogID: H1bRq5RwSkHdP+r99GmTVTAsFDG/5hNGCJ//rnldzC8=

Sectigoreadonly

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://sabre2026h2.ct.sectigo.com/

Sectigo Elephant2026h2
Dettagli tecnici

LogID: r2eIO1ewTt2Pptl+9i6o64EKx3Fg8CReVdYML+eFhzo=

Sectigousable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://elephant2026h2.ct.sectigo.com/

Sectigo Elephant2027h1
Dettagli tecnici

LogID: YEyar3p/d18B1Ab8kg3ImesLHH34yVIb+voXdzuXi8k=

Sectigousable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://elephant2027h1.ct.sectigo.com/

Sectigo Elephant2027h2
Dettagli tecnici

LogID: okkM3NuOM6QAMhdg1tTVGiA2GR6nfZaL4mqKAPb///c=

Sectigousable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://elephant2027h2.ct.sectigo.com/

Sectigo Tiger2026h2
Dettagli tecnici

LogID: yKPEf8ezrbk1awE/anoSbeM6TkOlxkb5l605dZkdz5o=

Sectigousable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://tiger2026h2.ct.sectigo.com/

Sectigo Tiger2027h1
Dettagli tecnici

LogID: HJ9oLOn68EVpUPgbloqH3dsyENhM5siy44JSSsTPWZ8=

Sectigousable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://tiger2027h1.ct.sectigo.com/

Sectigo Tiger2027h2
Dettagli tecnici

LogID: A4AqwmL24F4D+Lxve5hRMk/Xaj31t1lRdeIi+46b1fY=

Sectigousable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://tiger2027h2.ct.sectigo.com/

Sectigo Monument2027h1
Dettagli tecnici

LogID: lU+RNjI2rVhXzDYVRyLcQOf5ugowsOdS+/DHSylmVrg=

Sectigoqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://monument2027h1.sub.ct.sectigo.com/

monitoring_url: https://monument2027h1.mon.ct.sectigo.com/

Sectigo Monument2027h2
Dettagli tecnici

LogID: tvzC6p+E49qX4wl/sfIW6R/w154KB0QDJbBvlPXmU8U=

Sectigoqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://monument2027h2.sub.ct.sectigo.com/

monitoring_url: https://monument2027h2.mon.ct.sectigo.com/

Sectigo Monument2028h1
Dettagli tecnici

LogID: Mk28xZLuH+bg6aYx4WURJaunVGze9l0TxxGtWhs4aqk=

Sectigoqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://monument2028h1.sub.ct.sectigo.com/

monitoring_url: https://monument2028h1.mon.ct.sectigo.com/

Sectigo Monument2028h2
Dettagli tecnici

LogID: bHsR9YaIq7BLUlT3PyIbVVjgvpNRI3MlcGGfeugsbBA=

Sectigoqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://monument2028h2.sub.ct.sectigo.com/

monitoring_url: https://monument2028h2.mon.ct.sectigo.com/

Sectigo Statue2027h1
Dettagli tecnici

LogID: k0C4iKejzC796l4cBupj6U7f6w4VXgIIZFIAYZlMotE=

Sectigoqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://statue2027h1.sub.ct.sectigo.com/

monitoring_url: https://statue2027h1.mon.ct.sectigo.com/

Sectigo Statue2027h2
Dettagli tecnici

LogID: V+RgJ5TwE01vJbkN3nyKr9cuefY8ogzD9dFPs4lFv1U=

Sectigoqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://statue2027h2.sub.ct.sectigo.com/

monitoring_url: https://statue2027h2.mon.ct.sectigo.com/

Sectigo Statue2028h1
Dettagli tecnici

LogID: /Cvx3M57P/mNzO4pdqi0IuiOCa6pt5mhesjSWzqR+MA=

Sectigoqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://statue2028h1.sub.ct.sectigo.com/

monitoring_url: https://statue2028h1.mon.ct.sectigo.com/

Sectigo Statue2028h2
Dettagli tecnici

LogID: Zw/v+c0tZeC4UfTSi9vY+BdtNeIL3fhbQhT74s+jXiM=

Sectigoqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://statue2028h2.sub.ct.sectigo.com/

monitoring_url: https://statue2028h2.mon.ct.sectigo.com/

Let's Encrypt Oak2026h2
Dettagli tecnici

LogID: rKswcGzr7IQx9BPS9JFfER5CJEOx8qaMTzwrO6ceAsM=

Let's Encryptretired

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://oak.ct.letsencrypt.org/2026h2/

Let's Encrypt Sycamore2026h2
Dettagli tecnici

LogID: bP5QGUOoXqkWvFLRM+TcyR7xQRx9JYQg0XOAnhgY6zo=

Let's Encryptusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://log.sycamore.ct.letsencrypt.org/2026h2/

monitoring_url: https://mon.sycamore.ct.letsencrypt.org/2026h2/

Let's Encrypt Sycamore2027h1
Dettagli tecnici

LogID: jspHC6zeavOiBrCkeoS3Rv4fxr+VPiXmm07kAkjzxug=

Let's Encryptusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://log.sycamore.ct.letsencrypt.org/2027h1/

monitoring_url: https://mon.sycamore.ct.letsencrypt.org/2027h1/

Let's Encrypt Sycamore2027h2
Dettagli tecnici

LogID: 5eNiR9ku9K2jhYO1NZHbcp/C8ArktnRRdNPd/GqiU4g=

Let's Encryptusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://log.sycamore.ct.letsencrypt.org/2027h2/

monitoring_url: https://mon.sycamore.ct.letsencrypt.org/2027h2/

Let's Encrypt Willow2026h2
Dettagli tecnici

LogID: qCbL4wrGNRJGUz/gZfFPGdluGQgTxB3ZbXkAsxI8VSc=

Let's Encryptusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://log.willow.ct.letsencrypt.org/2026h2/

monitoring_url: https://mon.willow.ct.letsencrypt.org/2026h2/

Let's Encrypt Willow2027h1
Dettagli tecnici

LogID: ooEAGHNOF24dR+CVQPOBulRml81jqENQcW64CU7a8Q0=

Let's Encryptusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://log.willow.ct.letsencrypt.org/2027h1/

monitoring_url: https://mon.willow.ct.letsencrypt.org/2027h1/

Let's Encrypt Willow2027h2
Dettagli tecnici

LogID: ppWirZJtb5lujvxJAUJX2LvwRqfWJYm4jcLXh2x45S8=

Let's Encryptusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://log.willow.ct.letsencrypt.org/2027h2/

monitoring_url: https://mon.willow.ct.letsencrypt.org/2027h2/

Let's Encrypt Sycamore2028h1
Dettagli tecnici

LogID: G3i5n/pJwlzEUFl1q/10eRTf3fp7/dOdKjW5WQStPog=

Let's Encryptqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://log.sycamore.ct.letsencrypt.org/2028h1/

monitoring_url: https://mon.sycamore.ct.letsencrypt.org/2028h1/

Let's Encrypt Sycamore2028h2
Dettagli tecnici

LogID: d+CXC8fTD+AkXF2y76h1TAjrOpDdwSu11U7iiv4neHA=

Let's Encryptqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://log.sycamore.ct.letsencrypt.org/2028h2/

monitoring_url: https://mon.sycamore.ct.letsencrypt.org/2028h2/

Let's Encrypt Willow2028h1
Dettagli tecnici

LogID: caQ99zUpUI88YXJqTPeP+cknbMBSwvd3Zql1T9QKkMM=

Let's Encryptqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://log.willow.ct.letsencrypt.org/2028h1/

monitoring_url: https://mon.willow.ct.letsencrypt.org/2028h1/

Let's Encrypt Willow2028h2
Dettagli tecnici

LogID: vey1qmLph0NZ/U7NvnDZ8G8+j71Fo6xrycKFEbx0wJw=

Let's Encryptqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://log.willow.ct.letsencrypt.org/2028h2/

monitoring_url: https://mon.willow.ct.letsencrypt.org/2028h2/

TrustAsia log2026a
Dettagli tecnici

LogID: dNudWPfUfp39eHoWKpkcGM9pjafHKZGMmhiwRQ26RLw=

TrustAsiausable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://ct2026-a.trustasia.com/log2026a/

TrustAsia log2026b
Dettagli tecnici

LogID: Jbfv3qETAZPtkweXcKoyKiZiDeNayKp8dRl94LGp4GU=

TrustAsiausable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://ct2026-b.trustasia.com/log2026b/

TrustAsia HETU2027
Dettagli tecnici

LogID: 7drrgVxjITRJtHvlB3kFq9DZMUfCesUUazvFjkPptsc=

TrustAsiausable

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://hetu2027.trustasia.com/hetu2027/

TrustAsia Luoshu2027
Dettagli tecnici

LogID: VzRIzG4dLA3JS2nyh9Hv5IPHolxQxTILuzrep29usEE=

TrustAsiausable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://luoshu2027.trustasia.com/luoshu2027/

monitoring_url: https://luoshu2027.trustasia.com/luoshu2027/

TrustAsia Luoshu2028h1
Dettagli tecnici

LogID: cd1QREFkibQDp3c0FPKGnt4CnXEI84DXfoJshKW/fls=

TrustAsiaqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://luoshu2028h1.trustasia.com/luoshu2028h1/

monitoring_url: https://tile-luoshu2028h1.trustasia.com/luoshu2028h1/

TrustAsia Luoshu2028h2
Dettagli tecnici

LogID: jap0vUvSSHaUVxo2MsA8HZSVk3N5615qDROINcMzR8k=

TrustAsiaqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://luoshu2028h2.trustasia.com/luoshu2028h2/

monitoring_url: https://tile-luoshu2028h2.trustasia.com/luoshu2028h2/

TrustAsia Taiji2028h1
Dettagli tecnici

LogID: zVMsH8M+555WnWLXjKJmKkfeR5AsQ2zq+JS5GDG0BXw=

TrustAsiaqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://taiji2028h1.trustasia.com/taiji2028h1/

monitoring_url: https://tile-taiji2028h1.trustasia.com/taiji2028h1/

TrustAsia Taiji2028h2
Dettagli tecnici

LogID: 0J1XydPITy4G3x5te1QjepibtE1vlbKeTR/dmG3ySq4=

TrustAsiaqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://taiji2028h2.trustasia.com/taiji2028h2/

monitoring_url: https://tile-taiji2028h2.trustasia.com/taiji2028h2/

Bogus placeholder log to unbreak misbehaving CT libraries
Dettagli tecnici

LogID: LtakTeuPDIZGZ3acTt0EH4QjZ1X6OqymNNCTXfzVmnA=

Geomysretired

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://ct.example.com/bogus/

Geomys Tuscolo2026h2
Dettagli tecnici

LogID: Rq+GPTs+5Z+ld96oJF02sNntIqIj9GF3QSKUUu6VUF8=

Geomysusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://tuscolo2026h2.sunlight.geomys.org/

monitoring_url: https://tuscolo2026h2.skylight.geomys.org/

Geomys Tuscolo2027h1
Dettagli tecnici

LogID: WW5sM4aUsllyolbIoOjdkEp26Ag92oc7AQg4KBQ87lk=

Geomysusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://tuscolo2027h1.sunlight.geomys.org/

monitoring_url: https://tuscolo2027h1.skylight.geomys.org/

Geomys Tuscolo2027h2
Dettagli tecnici

LogID: 1d5V7roItgyf/BjFE75qYLoARga8WVuWu0T2LMV9Ofo=

Geomysusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://tuscolo2027h2.sunlight.geomys.org/

monitoring_url: https://tuscolo2027h2.skylight.geomys.org/

Geomys Tuscolo2028h1
Dettagli tecnici

LogID: TefD7+U3ZpoMsB44OPqv3PCMmoBWM55wK1iVm9FxiS4=

Geomysqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://tuscolo2028h1.sunlight.geomys.org/

monitoring_url: https://tuscolo2028h1.skylight.geomys.org/

Geomys Tuscolo2028h2
Dettagli tecnici

LogID: A18eYQnn44YBqbhkHlfl9aePeIcnUy/PQlPx68mqDzk=

Geomysqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://tuscolo2028h2.sunlight.geomys.org/

monitoring_url: https://tuscolo2028h2.skylight.geomys.org/

Geomys Trastevere2026h2
Dettagli tecnici

LogID: yMaDuhp5vKPNGyZsbZ6MzSf0hFEMerHyV59nUhBYOgM=

Geomysqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://trastevere2026h2.sunlight.geomys.org/

monitoring_url: https://trastevere2026h2.skylight.geomys.org/

Geomys Trastevere2027h1
Dettagli tecnici

LogID: F23RQr8KrLyBjUUTu9zDCtteWTJiU5KLmtfLdg/247k=

Geomysqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://trastevere2027h1.sunlight.geomys.org/

monitoring_url: https://trastevere2027h1.skylight.geomys.org/

Geomys Trastevere2027h2
Dettagli tecnici

LogID: dZIIKK86Y1XymO0JfjR1dfm5hDwR4TkfV0QpnxyujO4=

Geomysqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://trastevere2027h2.sunlight.geomys.org/

monitoring_url: https://trastevere2027h2.skylight.geomys.org/

Geomys Trastevere2028h1
Dettagli tecnici

LogID: j5ct6c9T2eqhZDHY6vWLWGZ8/QysT5c0VLGZaVHvlYc=

Geomysqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://trastevere2028h1.sunlight.geomys.org/

monitoring_url: https://trastevere2028h1.skylight.geomys.org/

Geomys Trastevere2028h2
Dettagli tecnici

LogID: y6VZ4BSDyZ+U7N2er0ezmWM1bZ/1wShe6un50SqgTMc=

Geomysqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://trastevere2028h2.sunlight.geomys.org/

monitoring_url: https://trastevere2028h2.skylight.geomys.org/

Bogus RFC6962 log to avoid breaking misbehaving CT libraries
Dettagli tecnici

LogID: 0vxlL6X5tzi4N1X6XrFfC0UlP06Po7m2T9TeVmLRhwg=

IPng Networksretired

86400
Inizio incluso
Fine esclusa
RFC 6962
Dettagli tecnici

url: https://ct.example.com/bogus/ipng/

IPng Networks Halloumi2026h2a
Dettagli tecnici

LogID: JuNkblhpISO8ND9HJDWbN5LNJFqI2BXTkzP9mRirRyM=

IPng Networksusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://halloumi2026h2a.log.ct.ipng.ch/

monitoring_url: https://halloumi2026h2a.mon.ct.ipng.ch/

IPng Networks Halloumi2027h1
Dettagli tecnici

LogID: ROgi/CurDpLu0On61pZkYCd20Bdg4IkFCckjobA/w38=

IPng Networksusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://halloumi2027h1.log.ct.ipng.ch/

monitoring_url: https://halloumi2027h1.mon.ct.ipng.ch/

IPng Networks Halloumi2027h2
Dettagli tecnici

LogID: CRV/Yy1Gx/dtlSZUk7wPALOVrF2zorJr+wQ9ukrGOJM=

IPng Networksusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://halloumi2027h2.log.ct.ipng.ch/

monitoring_url: https://halloumi2027h2.mon.ct.ipng.ch/

IPng Networks Gouda2026h2
Dettagli tecnici

LogID: Goudaw/+v4G0eTnG0jEKhtbRAtTwRuIYLJ3jX14mJe8=

IPng Networksusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://gouda2026h2.log.ct.ipng.ch/

monitoring_url: https://gouda2026h2.mon.ct.ipng.ch/

IPng Networks Gouda2027h1
Dettagli tecnici

LogID: Gouda43XkdHNBUnttgNV1ga2T60w23H+eI8Px8j7xLE=

IPng Networksusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://gouda2027h1.log.ct.ipng.ch/

monitoring_url: https://gouda2027h1.mon.ct.ipng.ch/

IPng Networks Gouda2027h2
Dettagli tecnici

LogID: GoudaVNi2GSSp7niI2BuNOzp4xC6NPuTBXhdKc5XV+s=

IPng Networksusable

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://gouda2027h2.log.ct.ipng.ch/

monitoring_url: https://gouda2027h2.mon.ct.ipng.ch/

IPng Networks Gouda2028h1
Dettagli tecnici

LogID: EgXQJVrBiTyuVBBwPE8Sc/yXAOErWEp/gGrcVVWAwLE=

IPng Networksqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://gouda2028h1.log.ct.ipng.ch/

monitoring_url: https://gouda2028h1.mon.ct.ipng.ch/

IPng Networks Gouda2028h2
Dettagli tecnici

LogID: ANXCUqZpzf6O0sgXpi5M/O2SyHSR7pccmv3bUoh4hag=

IPng Networksqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://gouda2028h2.log.ct.ipng.ch/

monitoring_url: https://gouda2028h2.mon.ct.ipng.ch/

IPng Networks Halloumi2028h1
Dettagli tecnici

LogID: 6+a9C+qJOkTtPzg+2/4QzZnxhphufXsmsBqEMk57934=

IPng Networksqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://halloumi2028h1.log.ct.ipng.ch/

monitoring_url: https://halloumi2028h1.mon.ct.ipng.ch/

IPng Networks Halloumi2028h2
Dettagli tecnici

LogID: ALNWz93lJLRlXUxjZTxSUMQ04goEhRA5uv1kzlyFq2s=

IPng Networksqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://halloumi2028h2.log.ct.ipng.ch/

monitoring_url: https://halloumi2028h2.mon.ct.ipng.ch/

Microsec Eszigno2026h2
Dettagli tecnici

LogID: KNPGjqGDY293g5DLHjiKzpOgTpFpnQdXNunGFtEf4Gc=

Microsecqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://eszigno2026h2.log.ct.e-szigno.hu/

monitoring_url: https://eszigno2026h2.mon.ct.e-szigno.hu/

Microsec Eszigno2027h1
Dettagli tecnici

LogID: eBAmYgxXrnCeBgs/iwSfqrh6aXhhDP+YpDWqAgNwe9k=

Microsecqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://eszigno2027h1.log.ct.e-szigno.hu/

monitoring_url: https://eszigno2027h1.mon.ct.e-szigno.hu/

Microsec Eszigno2027h2
Dettagli tecnici

LogID: GrnppF/Ct4QLH+fciv7lRpXau5p8I9NfpTclu4k6md0=

Microsecqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://eszigno2027h2.log.ct.e-szigno.hu/

monitoring_url: https://eszigno2027h2.mon.ct.e-szigno.hu/

Microsec Eszigno2028h1
Dettagli tecnici

LogID: bdyd6YsZgQp1oXcR+tZVoOVbdYzpKkXZg27d9PznIBM=

Microsecqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://eszigno2028h1.log.ct.e-szigno.hu/

monitoring_url: https://eszigno2028h1.mon.ct.e-szigno.hu/

Microsec Eszigno2028h2
Dettagli tecnici

LogID: 2iKjSO8buzFuV+ARSkqcdAe1DxOmJTk9JtLe4joj4hY=

Microsecqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://eszigno2028h2.log.ct.e-szigno.hu/

monitoring_url: https://eszigno2028h2.mon.ct.e-szigno.hu/

GoDaddy Aquamarine2026h2
Dettagli tecnici

LogID: 6jAGlJ1CunsD2FCB4yYsua5xil5vUDT3ePE4BU6CdFw=

GoDaddyqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://ct-log-api.godaddy.com/aquamarine2026h2/

monitoring_url: https://ct-log-api.godaddy.com/aquamarine2026h2/

GoDaddy Aquamarine2027h1
Dettagli tecnici

LogID: /cLoBbiE8/CzcwbEliJzk9OExUIiB/1Aj+4CBc6jVhY=

GoDaddyqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://ct-log-api.godaddy.com/aquamarine2027h1/

monitoring_url: https://ct-log-api.godaddy.com/aquamarine2027h1/

GoDaddy Aquamarine2027h2
Dettagli tecnici

LogID: 8LDBho1KJqIqj/7ghUOplCvvi7u69tYBqyHdvnFJ/68=

GoDaddyqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://ct-log-api.godaddy.com/aquamarine2027h2/

monitoring_url: https://ct-log-api.godaddy.com/aquamarine2027h2/

GoDaddy Aquamarine2028h1
Dettagli tecnici

LogID: Nh2PNG9+2gYj4hlfNqqVGKiHKCEzvpzppruUJGPrTaY=

GoDaddyqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://ct-log-api.godaddy.com/aquamarine2028h1/

monitoring_url: https://ct-log-api.godaddy.com/aquamarine2028h1/

GoDaddy Aquamarine2028h2
Dettagli tecnici

LogID: /jwyxS3R1tXbsRUdYe6iH5EhBfIZa1UNh/as89aPnFM=

GoDaddyqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://ct-log-api.godaddy.com/aquamarine2028h2/

monitoring_url: https://ct-log-api.godaddy.com/aquamarine2028h2/

HARICA Selene2027h1
Dettagli tecnici

LogID: g92PTAqC4jctZFmPZBgRxF27h4JAz96XF7b9cOQAZ4c=

HARICAqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://selene.ct.harica.eu/selene2027h1/

monitoring_url: https://selene.mon.ct.harica.eu/selene2027h1/

HARICA Selene2027h2
Dettagli tecnici

LogID: sYdPqlxcQTingZPPo7kk2ImvyDNpOcfp+q0JVhrGpV4=

HARICAqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://selene.ct.harica.eu/selene2027h2/

monitoring_url: https://selene.mon.ct.harica.eu/selene2027h2/

HARICA Selene2028h1
Dettagli tecnici

LogID: GZ9TRtShpGoaPdygptJx/Taqms3LslRJmOM+dVHZi8k=

HARICAqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://selene.ct.harica.eu/selene2028h1/

monitoring_url: https://selene.mon.ct.harica.eu/selene2028h1/

HARICA Selene2028h2
Dettagli tecnici

LogID: +ZgQ1evkfhzxtCH/beNb+MHsluJeBNv8dW9r5FxlXMo=

HARICAqualified

60
Inizio incluso
Fine esclusa
static-ct-api
Dettagli tecnici

submission_url: https://selene.ct.harica.eu/selene2028h2/

monitoring_url: https://selene.mon.ct.harica.eu/selene2028h2/

Source provenance and file checks

Source-file checks: JSON schema v3 validated; detached signature verified with Google’s published RSA 4096-bit key, RSASSA-PKCS1-v1_5 / SHA-256; all 89 LogIDs checked against SHA-256 of DER keys. These checks concern the downloaded list, not certificate or SCT signatures, inclusion proofs or current service state.

Source JSON SHA-256
d950288c2750fb6f7725880e897a3eaf7b7c769cf822d5940c2b3b213e32a211
Public key PEM SHA-256
a284e4ad744211a6636a03c59aca9446ecd5ff2c14d7cb6edd69f7ba2108bf95

Google Chrome · log_list.json · Published public key ·

Investigation cases: turn a signal into a question

Investigation cases: turn a signal into a question
Fictional observationCheck to prepareProportionate conclusion
A name appears in certificate SANsRecord exact name, issuer, serial number, dates and source. Separately check authorised, dated DNS and TLS observations.“Name present in an observed certificate”, without claiming the server still exists.
The same certificate appears in multiple logsMatch the exact object by its fingerprint and distinguish logging occurrences. Separate final certificates, precertificates and renewals.Multiple occurrences are not multiple services or multiple compromises.
A certificate contains *.example.orgPreserve the wildcard as such. Do not manufacture hostnames from that entry alone.The pattern does not enumerate deployed subdomains.
A search returns no resultDocument the tool, covered logs, query, time and possible collection delay.No result within this scope, without claiming no certificate or asset exists.
An SCT is dated 12:00 UTC, with MMD = 60 sThe theoretical incorporation deadline is 12:01 UTC. Examine the promise using the appropriate log objects and proofs.A missing search result at 12:00:30 does not demonstrate an MMD violation.

Google Chrome · Certificate Transparency for Site Operators · Domain Privacy · consulted 2026-10-23

IETF · RFC 5280 · X.509 certificate profile · May 2008 · §§4.1.2.5, 4.2.1.6, 6

Make a trace usable in an intelligence note

  1. Define collection scope

    Record domain or pattern, primary source or aggregator, UTC time and scope. A search source may have its own coverage and lag.

  2. Keep object and context

    Distinguish certificate, precertificate, SCT and proof. Associate object fingerprint, LogID, leaf index or tree size where available, and consultation time.

  3. Corroborate across layers

    Compare registration data, DNS, TLS and web content with their respective dates. Shared infrastructure can explain technical links without an organisational relationship.

  4. Express uncertainty

    Separate observations, inferences and points still requiring confirmation. Assign an owner and next check to any hypothesis that influences a decision.

Data: Google Chrome, documentary investigation and audit use under its usage policy. The snapshot is not a trust store and is not used for CT enforcement in a TLS client. Analysis tables, prose and fictional examples are CIE editorial synthesis; linked documents retain their own terms.

Google Chrome · CT Log Lists and usage policy · Consulted 2026-11-07

RDAP: registrazione, ruoli e dati oscurati

Le note dettagliate di questa edizione sono disponibili in inglese.

RDAP: qualify the role before naming an actor

Registrar, registrant and technical contact answer different questions. A public registration response is dated and may contain unpublished data.

  • Read declared roles instead of matching names alone.
  • Separate registration, change, synchronisation and collection dates.
  • Retain redactions and access limitations without inventing the missing identity.

Open the RDAP dossier and local reader →

IETF · RFC 9083 · RDAP JSON Responses · June 2021 · §§4–5, 9–10

Catene di citazioni e ascolto sociale

Le note dettagliate di questa edizione sono disponibili in inglese.

Separate origin, repost and corroboration

A capture or provenance signature may document a record without proving its claim. Before citing multiple publications, check whether they reference the same document.

  • Keep the consulted version and its exact reference.
  • Name missing citations instead of assuming their contents.
  • Treat distinct documents as records to compare, without assuming independence.

Read the method and explore citation chains →

Government Communications · RESIST 3 · RESIST 3 · 2025 · consulted 2026-10-23

Government Communications · RESIST 3 quick reference · RESIST 3 · 2025 · consulted 2026-10-23

Riferimenti ufficiali

I riferimenti supportano il metodo. Adattare i controlli al proprio contesto; non costituiscono una certificazione. I titoli dei riferimenti originali e i documenti di origine potrebbero essere in un'altra lingua.

Riferimenti consultati il .