Google common crawlers
315 Bereiche · Quelldatum 2026-08-21
Crawler-Verzeichnis
Bot-IP-Bereiche
Ein lokales schreibgeschütztes Verzeichnis ausschließlich aus offiziellen Google- und Microsoft-Feeds.
Alle 30 Tage aktualisiert
1.669
IPv4 860 · IPv6 809
IP prüfen oder Quelle filtern
Die Suche erfolgt im lokalen Datenbestand, ohne die eingegebene Adresse zu kontaktieren.
Offizielle Quellen
1.669 passende Bereiche
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:70::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:71::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:72::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:73::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:74::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:75::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:76::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:77::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:78::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:79::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:7a::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:7b::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:7c::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:7d::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:7e::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:7f::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:80::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:81::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:82::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:83::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:84::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:85::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:86::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:87::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:88::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:89::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:8::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:8a::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:8b::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:90::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:91::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:92::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:93::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:94::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:95::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:96::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:97::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:98::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:99::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:9::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:a0::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:a1::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:a2::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:a3::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:a4::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:a5::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:a6::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:b0::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:b1::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:b2::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:b3::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:b4::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:b5::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:b6::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:b7::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:b8::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:b9::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:ba::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:bb::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:bc::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:bd::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:c0::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:c1::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:c2::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:c3::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:c4::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:c5::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:c6::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:c::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:d0::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:d1::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:d2::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:d3::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:d4::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:d5::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:d6::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:d7::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:d8::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:d9::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:da::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:db::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:dc::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:dd::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:de::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:df::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:e0::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:e1::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:e2::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:e3::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:e4::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:e5::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:e6::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:e7::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:e8::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:e9::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:ea::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:eb::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:ec::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:ed::/64 | |
| Google user-triggered fetchers | IPv6 | 2600:1900:0:ee::/64 |
Serversicherheit
Feste, validierte und begrenzte Feeds
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.
Google special crawlers
270 Bereiche · Quelldatum 2026-08-21
Google user-triggered fetchers
1056 Bereiche · Quelldatum 2026-08-21
Bingbot
28 Bereiche · Quelldatum 2024-01-03