PageSourceSearch

https://www.leegle.ai/

html leegle.ai collected 2026-10-05 12:10:01 UTC 1,810 bytes, 27 lines download raw bytes

1<!doctype html>
2<html lang="de">
3  <head>
4    <meta charset="UTF-8" />
5    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
6    <link rel="icon" type="image/png" href="/favicon.png">
7    <title>Leegle — AI-native Regulatory &amp; Compliance OS</title>
8    <meta name="description" content="Leegle übersetzt regulatorische Komplexität in klare, produktspezifische Anforderungen — automatisch, nachvollziehbar, audit-bereit.">
9    <meta name="author" content="Leegle" />
10    
11    
12    <meta property="og:type" content="website" />
13    <meta name="twitter:card" content="summary_large_image" />
14    <meta property="og:title" content="Leegle — AI-native Regulatory &amp; Compliance OS">
15  <meta name="twitter:title" content="Leegle — AI-native Regulatory &amp; Compliance OS">
16  <meta property="og:description" content="Leegle übersetzt regulatorische Komplexität in klare, produktspezifische Anforderungen — automatisch, nachvollziehbar, audit-bereit.">
17  <meta name="twitter:description" content="Leegle übersetzt regulatorische Komplexität in klare, produktspezifische Anforderungen — automatisch, nachvollziehbar, audit-bereit.">
18  <meta property="og:image" content="https://storage.googleapis.com/gpt-engineer-file-uploads/h4ktf7fLPORfD9rOFUWO3UFbJX33/social-images/social-1776270246679-og-default.webp">
19  <meta name="twitter:image" content="https://storage.googleapis.com/gpt-engineer-file-uploads/h4ktf7fLPORfD9rOFUWO3UFbJX33/social-images/social-1776270246679-og-default.webp">
20  
20<script type="module" crossorigin src="/assets/index-oBnpLKeb.js"></script>
20
21  <link rel="stylesheet" crossorigin href="/assets/index-CFAku8oT.css">
22<script defer src="/~flock.js" data-proxy-url="/~api/analytics"></script>
22</head>
23
24  <body>
25    <div id="root"></div>
26  </body>
27</html>

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.