- ID de exploración:
- c3ec7aac-eb11-44c5-bfaa-0f99fa47b7faFinalizado
- URL enviada:
- https://certificate-transparency.org/Redireccionado
- Informe finalizado:
Enlaces: 11 encontrados
Los enlaces salientes identificados en la página
| Enlace | TEXTO |
|---|---|
| https://github.com/google/certificate-transparency-go | GitHub page |
| https://groups.google.com/forum/#!forum/certificate-transparency | Google Group. |
| https://apple.com | |
| https://github.com/chromium/ct-policy/blob/master/ct_policy.md#qualifying-certificate | |
| https://censys.io/certificates | |
| https://developers.cloudflare.com/ssl/certificate-transparency-monitoring | |
| https://www.digicert.com/certificate-transparency/overview.htm | |
| https://www.facebook.com/notes/protect-the-graph/introducing-our-certificate-transparency-monitoring-tool/1811919779048165/ | |
| https://letsencrypt.org/2019/11/20/how-le-runs-ct-logs.html | |
| https://sectigo.com/ssl-certificates-tls |
Variables JavaScript: 36 encontradas
Las variables JavaScript globales cargadas en el objeto de ventana de una página son variables declaradas fuera de las funciones y a las que se puede acceder desde cualquier lugar del código en el ámbito actual
| Nombre | Tipo |
|---|---|
| 0 | object |
| 1 | object |
| 2 | object |
| 3 | object |
| 4 | object |
| 5 | object |
| 6 | object |
| 7 | object |
| 8 | object |
| 9 | object |
Mensajes de registro de la consola: 1 encontrados
Mensajes registrados en la consola web
| Tipo | Categoría | Registrar |
|---|---|---|
| log | other |
|
HTML
El cuerpo HTML sin procesar de la página
<!DOCTYPE html><html lang="en"><head>
<meta name="generator" content="Hugo 0.83.1">
<meta charset="utf-8">
<meta name="description" content="Certificate Transparency">
<link rel="shortcut icon" type="image/png" href="https://certificate.transparency.dev/img/favicon.png">
<title>
Certificate Transparency : Certificate Transparency
</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link href="https://fonts.googleapis.com/css?family=Inter:700,800&display=swap" rel="stylesheet">
<link rel="stylesheet" href="/css/ct.adf8bf421069b5b03cf4d994a2913eb75f3b785979067dc040e4f5b86022928a.css">
<script type="text/javascript" src="https://certificate.transparency.dev/js/bundle.min.a172990f9e737116fc6b86f21a72b6b1d9c4a87b7e1c4132bf179d95798baf06.js"></script>
</head>
<body id="scheme-home">
<div id="page-container">
<div id="content-container">
<nav id="top">
<div id="brand"><a href="/">Certificate Transparency</a></div>
<div id="mobilemenu-controls">
<a class="hide-menu" href="#">×</a>
<a class="show-menu" href="#">☰</a>
</div>
<div class="menus">
<ul class="menu">
<li class="howctworks"><a href="/howctworks" title="How Certificate Transparency works">How CT works</a></li>
<li class="submenu-target">
<span>
Actors
<svg xmlns="http://www.w3.org/2000/svg" class="dropdown-triangle">
<polygon points="0,0 10,0 5,8"></polygon>
</svg>
</span>
<ul class="submenu">
<li class="logs"><a href="/logs" title="Certificate Transparency Logs">Logs</a></li>
<li class="monitors"><a href="/monitors" title="Certificate Transparency Monitors">Monitors</a></li>
<li class="user_agents"><a href="/useragents" title="Certificate Transparency User Agents">User Agents</a></li>
</ul>
</li>
<li class="community"><a href="/community" title="Story of Certificate Transparency">Our story</a></li>
</ul>
<ul class="elsewhere">
<li class="github"><a href="https://github.com/google/certificate-transparency-go" title="Certificate Transparency GitHub">GitHub</a></li>
<li class="ggroup"><a href="https://groups.google.com/forum/#!forum/certificate-transparency" title="Certificate Transparency Google Group">Google Group</a></li>
</ul>
</div>
</nav>
<div id="nav-shield"></div>
<section>
<div class="wrap-outer">
<div class="wrap">
<div class="page-heading almost-full">
<h1>Working together to detect maliciously or mistakenly issued certificates.</h1>
</div>
</div>
</div>
</section>
<div class="wrap-outer noscroll">
<div class="wrap">
<div class="home-illustration">
<object title="Certificate Transparency" class="sm svg-obj" type="image/svg+xml" data-animate-svg-selector=".anim" data-animated-stroke-width="2px" data="https://certificate.transparency.dev/img/small/home-illustration.svg"></object>
<object title="Certificate Transparency" class="md svg-obj" type="image/svg+xml" data-animate-svg-selector=".anim" data-animated-stroke-width="2px" data="https://certificate.transparency.dev/img/home-illustration.svg"></object>
</div>
</div>
</div>
<section id="home-postimage">
<div class="wrap">
<h2 class="mid">
An ecosystem that makes the issuance of website certificates <strong>transparent</strong> and <strong>verifiable.</strong>
</h2>
</div>
</section>
<section id="home-credits">
<div class="wrap-outer">
<div class="wrap">
<p class="thanks-small">
To the participants of the Certificate Transparency (CT) ecosystem, who give their time, expertise, and resources to help keep the web secure.
</p>
<ul class="operators">
<li>
<a title="Apple" href="https://apple.com">
<img src="img/collab-logos/apple.svg" alt="Apple logo">
</a>
</li>
<li>
<a title="Google" href="https://github.com/chromium/ct-policy/blob/master/ct_policy.md#qualifying-certificate">
<img src="img/collab-logos/google.svg" alt="Google logo">
</a>
</li>
<li>
<a title="Censys" href="https://censys.io/certificates">
<img style="width: 130px" src="img/collab-logos/censys.png" alt="Censys logo">
</a>
</li>
<li>
<a title="Cloudflare" href="https://developers.cloudflare.com/ssl/certificate-transparency-monitoring">
<img src="img/collab-logos/cloudflare.svg" alt="Cloudflare logo">
</a>
</li>
<li>
<a title="Digicert" href="https://www.digicert.com/certificate-transparency/overview.htm">
<img src="img/collab-logos/digicert.svg" alt="Digicert logo">
</a>
</li>
<li>
<a title="Facebook" href="https://www.facebook.com/notes/protect-the-graph/introducing-our-certificate-transparency-monitoring-tool/1811919779048165/">
<img src="img/collab-logos/facebook.png" alt="Facebook logo">
</a>
</li>
<li>
<a title="Let's Encrypt" href="https://letsencrypt.org/2019/11/20/how-le-runs-ct-logs.html">
<img src="img/collab-logos/lets-encrypt.svg" alt="Let's Encrypt logo">
</a>
</li>
<li>
<a title="Sectigo" href="https://sectigo.com/ssl-certificates-tls">
<img src="img/collab-logos/sectigo.svg" alt="Sectigo logo">
</a>
</li>
<li>
<a title="SSLMate" href="https://sslmate.com/certspotter/">
<img src="img/collab-logos/sslmate.svg" alt="SSLMate logo">
</a>
</li>
</ul>
<p class="thanks-large">Thank you.</p>
</div>
</div>
</section>
<section id="home-details">
<div class="wrap-outer noscroll">
<div class="wrap">
<div class="details-segment image-right">
<object title="A cryptographic key is bound to a domain name" class="svg-obj sm" type="image/svg+xml" data-animate-svg-selector=".anim" data="https://certificate.transparency.dev/img/small/home2.svg"></object>
<object title="A cryptographic key is bound to a domain name" class="svg-obj md" type="image/svg+xml" data-animate-svg-selector=".anim" data="https://certificate.transparency.dev/img/home2.svg"></object>
<h3>Certificates, encryption, and secure communication </h3>
<p>Certificate Transparency (CT) sits within a wider ecosystem, Web Public Key Infrastructure. Web PKI includes everything needed to issue and verify certificates used for TLS on the web. Certificates bind a public cryptographic key to a domain name, similar to how a passport brings together a person's photo and name.</p>
</div>
<div class="details-segment image-left">
<object title="A certificate" class="svg-obj sm" type="image/svg+xml" data-animate-svg-selector=".anim" data="https://certificate.transparency.dev/img/small/home3.svg"></object>
<object title="A certificate" class="svg-obj md" type="image/svg+xml" data-animate-svg-selector=".anim" data="https://certificate.transparency.dev/img/home3.svg"></object>
<h3>Certificate Authorities (CAs) play an important role</h3>
<p>Certificates are issued by CAs. Web PKI requires user agents and domain owners to trust that CAs are tying domains to the right domain owners. A user agent is something that acts on behalf of a user, usually a browser.</p>
</div>
<div class="details-segment image-right">
<object title="Many certificate authorities" class="svg-obj sm" type="image/svg+xml" data-animate-svg-selector=".anim" data="https://certificate.transparency.dev/img/small/home4.svg"></object>
<object title="Many certificate authorities" class="svg-obj md" type="image/svg+xml" data-animate-svg-selector=".anim" data="https://certificate.transparency.dev/img/home4.svg"></object>
<h3>What if a CA can’t be trusted?</h3>
<p>A CA that has been hacked or sloppy can issue certificates for any website. The communication would still be technically encrypted, but there could be an attacker at the other end who could intercept the private data.</p>
</div>
<div class="details-segment image-left">
<object title="Audits of certificate authorities" class="svg-obj sm" type="image/svg+xml" data-animate-svg-selector=".anim" data="https://certificate.transparency.dev/img/small/home5.svg"></object>
<object title="Audits of certificate authorities" class="svg-obj md" type="image/svg+xml" data-animate-svg-selector=".anim" data="https://certificate.transparency.dev/img/home5.svg"></object>
<h3>Who watches the watchers?</h3>
<p>Historically, user agents determined if CAs were trustworthy through audits by credentialled third parties.
But these tended to look at operational practices and historical performance rather than technical
correctness. Such audits can’t catch everything. Before CT, there could be a significant time lag between a
certificate being wrongly issued, and a CA doing something about it.</p>
</div>
</div>
</div>
<div class="wrap-outer backdrop hero">
<div class="wrap">
<div class="details-segment hero">
<div class="inner tight">
That's where<br>
<span>Certificate Transparency</span><br>
comes in.
</div>
</div>
</div>
</div>
<div class="wrap-outer noscroll">
<div class="wrap">
<div class="details-segment image-right">
<object title="Reliable logs" class="svg-obj sm" type="image/svg+xml" data-animate-svg-selector=".anim" data="https://certificate.transparency.dev/img/small/home6.svg"></object>
<object title="Reliable logs" class="svg-obj md last" type="image/svg+xml" data-animate-svg-selector=".anim" data="https://certificate.transparency.dev/img/home6.svg"></object>
<h3>Independent, reliable logs</h3>
<p>CT depends on independent, reliable logs because it is a distributed ecosystem. Built using Merkle trees, logs are publicly verifiable, append-only, and tamper-proof.</p>
</div>
<div class="details-segment hero">
<span class="small">Since 2013</span>
<span id="cert-count" class="cert-count">2,563,437,540</span>
<span class="small">certificates have been logged</span>
</div>
<div class="details-segment image-left">
<object title="Logs are monitored" class="svg-obj sm" type="image/svg+xml" data-animate-svg-selector=".anim" data="https://certificate.transparency.dev/img/small/home7.svg"></object>
<object title="Logs are monitored" class="svg-obj md" type="image/svg+xml" data-animate-svg-selector=".anim" data="https://certificate.transparency.dev/img/home7.svg"></object>
<h3>Logs are publicly available and monitored</h3>
<p>Thanks to CT, domain owners, browsers, academics, and other interested people can analyse and monitor logs.
They’re able to see which CAs have issued which certificates, when, and for which domains. </p>
</div>
<div class="details-segment image-right">
<object title="Independent organizations run logs" class="svg-obj sm" type="image/svg+xml" data-animate-svg-selector=".anim" data="https://certificate.transparency.dev/img/small/home8.svg"></object>
<object title="Independent organizations run logs" class="svg-obj md last" type="image/svg+xml" data-animate-svg-selector=".anim" data="https://certificate.transparency.dev/img/home8.svg"></object>
<h3>Protect the web by running a CT log</h3>
<p>To help keep the web safe, CT needs numerous robust logs, run by different organizations, in different
jurisdictions.</p>
<p>CT may have been started by engineers at Google, but it works because independent organizations set up and
run monitors and logs. For the internet, and of the internet.</p>
</div>
</div>
</div>
<span class="clear">
<!-- clear--></span>
</section>
<div id="bigfooter">
<div class="wrap-outer noscroll">
<div class="inner">
<p><a href="https://certificate.transparency.dev/howctworks/" title="Find out how Certificate Transparency works">Find out more</a> about how<br> Certificate Transparency works.</p>
<p>
Or get started by going to the <a href="https://github.com/google/certificate-transparency-go" title="Certificate Transparency GitHub">GitHub page</a><br>
or joining the <a href="https://groups.google.com/forum/#!forum/certificate-transparency" title="Certificate Transparency Google Group">Google Group.</a></p>
</div>
</div>
</div>
</div>
<div id="footer-container">
<div id="footer">
<div class="row">
<h3>Certificate Transparency</h3>
<ul class="footer-menu">
<li><a href="/howctworks" title="How Certificate Transparency works">How CT works</a></li>
<li><a href="/community" title="Story of Certificate Transparency">Our story</a></li>
</ul>
</div>
<div class="row rev">
<ul class="footer-menu">
<li>
<ul>
<li><a href="/logs" title="Certificate Transparency Logs">Logs</a></li>
<li><a href="/monitors" title="Certificate Transparency Monitors">Monitors</a></li>
<li><a href="/useragents" title="Certificate Transparency User Agents">User agents</a></li>
</ul>
</li>
<li>
<ul>
<li><a href="https://github.com/google/certificate-transparency-go" title="Certificate Transparency Github">GitHub</a></li>
<li><a href="https://groups.google.com/forum/#!forum/certificate-transparency" title="Certificate Transparency Google Group">Google Group</a></li>
</ul>
</li>
</ul>
<div class="tag">
<span>
Started by engineers at Google,<br>
<strong>for the internet.</strong>
</span>
</div>
</div>
</div>
</div>
</div>
</body></html>