Google common crawlers
315 Bereiche · Quelldatum 2026-08-21
Crawler-Verzeichnis
Ein lokales schreibgeschütztes Verzeichnis ausschließlich aus offiziellen Google- und Microsoft-Feeds.
Die Suche erfolgt im lokalen Datenbestand, ohne die eingegebene Adresse zu kontaktieren.
Offizielle Quellen
Datenstand: 2026-08-21 22:11 UTC. Nächste geplante Aktualisierung: 2026-09-20.
| Anbieter | Quelle | Familie | CIDR |
|---|---|---|---|
| Google user-triggered fetchers | IPv6 | 2600:1900:0:18::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:18a::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:18b::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:18c::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:18d::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:18e::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:18f::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:190::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:191::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:192::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:193::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:194::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:195::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:196::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1a0::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1a1::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1a2::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1a3::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1a::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1b::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1c0::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1c1::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1c2::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1c3::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1c4::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1c5::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1c6::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1c::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1d0::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1d1::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1e0::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1e1::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1e2::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1e3::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1e4::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1f0::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1f1::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1f2::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1f3::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1f4::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1f5::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1f6::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1f7::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:1f8::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:200::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:201::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:202::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:203::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:204::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:205::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:206::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:207::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:208::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:209::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:20::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:20a::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:20b::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:210::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:211::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:212::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:213::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:214::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:215::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:216::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:217::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:21::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:220::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:221::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:222::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:223::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:22::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:230::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:231::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:232::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:233::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:234::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:235::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:236::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:237::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:238::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:239::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:23::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:23a::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:23b::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:240::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:241::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:242::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:24::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:250::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:251::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:252::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:253::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:254::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:255::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:25::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:260::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:261::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:262::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:263::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:264::/64 |
Serversicherheit
Nur vier fest hinterlegte HTTPS-URLs werden geladen. Weiterleitungen werden abgelehnt, Größe und Anzahl sind begrenzt, CIDRs werden validiert und der Datenstand nur nach Erfolg aller Feeds atomar ersetzt.
315 Bereiche · Quelldatum 2026-08-21
270 Bereiche · Quelldatum 2026-08-21
1056 Bereiche · Quelldatum 2026-08-21
28 Bereiche · Quelldatum 2024-01-03