.zeabur.app
Scaricare i domini .zeabur.app
355 domini attivi
Suffisso pubblico · Sotto .app · Gestita da Google Registry
Suffisso TLD
Dataset aggiornato · 2026-08-30
🔒 Ottenere la lista
A partire da €29 / mese
Informazioni su .zeabur.app
.zeabur.app è un suffisso pubblico multilivello situato un livello sotto .app. Suffissi come questo esistono perché i registri riservano un secondo livello a categorie specifiche di titolari di domini. I titolari li trattano come se fossero TLD di primo livello, e lo stesso vale per i dataset di webatla.
A colpo d’occhio
Tutti i dati aggiornati in data 30 ago 2026
Nuove registrazioni di domini
3
la settimana scorsa
27
il mese scorso
Domini attivi355
domini registrati e attivi nella zona .zeabur.app
Siti web attivi355
siti web attivi nella zona .zeabur.app
DNS355
domini con record DNS
Paesi13
paesi rappresentati (per IP di hosting)
RDAP & WHOIS217
domini con record RDAP e WHOIS
Anteprima del database dei domini .zeabur.app
5 righe di esempio dal database in tempo reale. Cambi dataset per vedere cosa contiene ciascuno, poi consulti il file o acquisti il dataset completo.
webatla-zeabur-app-all-2026-08-30.jsonl.zst · 355 righe · 23 colonne
Esportazione giornaliera aggiornata
| Domain | TLD suffix | TLD | Domain type |
|---|---|---|---|
| zeabur.app.zeabur.app | zeabur.app | app | PRIVATE |
| 2025-vibe-coding-frontend.zeabur.app | zeabur.app | app | PRIVATE |
| allenblog.zeabur.app | zeabur.app | app | PRIVATE |
| amami.zeabur.app | zeabur.app | app | PRIVATE |
| amnfrrpro.zeabur.app | zeabur.app | app | PRIVATE |
| … | … | … | … |
| Domain | TLD suffix | TLD | Domain type | Country by IP | PR value | Harmonic value | Domain creation date | Domain expiration date |
|---|---|---|---|---|---|---|---|---|
| zeabur.app.zeabur.app | zeabur.app | app | PRIVATE | US | 0.000000129257 | 17,656,562 | — | — |
| 2025-vibe-coding-frontend.zeabur.app | zeabur.app | app | PRIVATE | HK | 0 | 0 | — | — |
| allenblog.zeabur.app | zeabur.app | app | PRIVATE | HK | 0 | 0 | — | — |
| amami.zeabur.app | zeabur.app | app | PRIVATE | US | 0 | 0 | — | — |
| amnfrrpro.zeabur.app | zeabur.app | app | PRIVATE | US | 0 | 0 | — | — |
| … | … | … | … | … | … | … | … | … |
| Domain | TLD suffix | TLD | Domain type | HTTP status | IP address | Country by IP | Social networks | Technologies last data checked | Technologies | PR value | Harmonic value | Domain creation date | Domain expiration date |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| zeabur.app.zeabur.app | zeabur.app | app | PRIVATE | HTTP 404 | 52.223.32.133 | US | — | 2026-08-23 | Unpkg, HTTP/3, Tailwind CSS | 0.000000129257 | 17,656,562 | — | — |
| 2025-vibe-coding-frontend.zeabur.app | zeabur.app | app | PRIVATE | HTTP 200 | 43.199.8.212 | HK | {"discord":["https://discord.com/channels/801807326054055996/1428276906691792988"]} | 2026-08-24 | Caddy, cdnjs, HTTP/3, Vue.js, Favicon, Node.js, Nuxt.js, Cloudflare, Open Graph, Font Awesome 5.15.4 | 0 | 0 | — | — |
| allenblog.zeabur.app | zeabur.app | app | PRIVATE | HTTP 404 | 43.199.8.212 | HK | — | 2026-08-26 | Unpkg, HTTP/3, Tailwind CSS | 0 | 0 | — | — |
| amami.zeabur.app | zeabur.app | app | PRIVATE | HTTP 404 | 52.223.32.133 | US | — | 2026-08-26 | Unpkg, HTTP/3, Tailwind CSS | 0 | 0 | — | — |
| amnfrrpro.zeabur.app | zeabur.app | app | PRIVATE | HTTP 404 | 52.223.32.133 | US | — | 2026-08-26 | Unpkg, HTTP/3, Tailwind CSS | 0 | 0 | — | — |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … |
| Domain | TLD suffix | TLD | Domain type | DNS last data checked | DNS Status | DNS records |
|---|---|---|---|---|---|---|
| zeabur.app.zeabur.app | zeabur.app | app | PRIVATE | 2026-08-14 | TRUE | {"A":["52.223.32.133"]} |
| 2025-vibe-coding-frontend.zeabur.app | zeabur.app | app | PRIVATE | 2026-08-29 | TRUE | {"A":["43.199.8.212"],"CNAME":["hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com"]} |
| allenblog.zeabur.app | zeabur.app | app | PRIVATE | 2026-08-18 | TRUE | {"A":["43.199.8.212"],"CNAME":["hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com"]} |
| amami.zeabur.app | zeabur.app | app | PRIVATE | 2026-08-18 | TRUE | {"A":["52.223.32.133"]} |
| amnfrrpro.zeabur.app | zeabur.app | app | PRIVATE | 2026-08-15 | TRUE | {"A":["52.223.32.133"]} |
| … | … | … | … | … | … | … |
| Domain | RDAP/WHOIS last data checked | RDAP/WHOIS method | Domain creation date | Domain expiration date | Domain last changed | Registrar | RDAP/WHOIS Record | Response Status RDAP/WHOIS |
|---|---|---|---|---|---|---|---|---|
| zeabur.app.zeabur.app | — | — | — | — | — | — | — | — |
| 2025-vibe-coding-frontend.zeabur.app | — | — | — | — | — | — | — | — |
| allenblog.zeabur.app | — | — | — | — | — | — | — | — |
| amami.zeabur.app | — | — | — | — | — | — | — | — |
| amnfrrpro.zeabur.app | — | — | — | — | — | — | — | — |
| … | … | … | … | … | … | … | … | … |
| Domain | TLD suffix | TLD | Domain type | HTTP status | IP address | Country by IP | Social networks | Technologies last data checked | Technologies | DNS last data checked | DNS Status | DNS records | PR value | Harmonic value | RDAP/WHOIS last data checked | RDAP/WHOIS method | Domain creation date | Domain expiration date | Domain last changed | Registrar | RDAP/WHOIS Record | Response Status RDAP/WHOIS |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| zeabur.app.zeabur.app | zeabur.app | app | PRIVATE | HTTP 404 | 52.223.32.133 | US | — | 2026-08-23 | Unpkg, HTTP/3, Tailwind CSS | 2026-08-14 | TRUE | {"A":["52.223.32.133"]} | 0.000000129257 | 17,656,562 | — | — | — | — | — | — | — | — |
| 2025-vibe-coding-frontend.zeabur.app | zeabur.app | app | PRIVATE | HTTP 200 | 43.199.8.212 | HK | {"discord":["https://discord.com/channels/801807326054055996/1428276906691792988"]} | 2026-08-24 | Caddy, cdnjs, HTTP/3, Vue.js, Favicon, Node.js, Nuxt.js, Cloudflare, Open Graph, Font Awesome 5.15.4 | 2026-08-29 | TRUE | {"A":["43.199.8.212"],"CNAME":["hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com"]} | 0 | 0 | — | — | — | — | — | — | — | — |
| allenblog.zeabur.app | zeabur.app | app | PRIVATE | HTTP 404 | 43.199.8.212 | HK | — | 2026-08-26 | Unpkg, HTTP/3, Tailwind CSS | 2026-08-18 | TRUE | {"A":["43.199.8.212"],"CNAME":["hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.cname.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","hkg1.ingress.zeabur-dns.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com","zeabur-ingress-hkg1-fd15e3e87b428c41.elb.ap-east-1.amazonaws.com"]} | 0 | 0 | — | — | — | — | — | — | — | — |
| amami.zeabur.app | zeabur.app | app | PRIVATE | HTTP 404 | 52.223.32.133 | US | — | 2026-08-26 | Unpkg, HTTP/3, Tailwind CSS | 2026-08-18 | TRUE | {"A":["52.223.32.133"]} | 0 | 0 | — | — | — | — | — | — | — | — |
| amnfrrpro.zeabur.app | zeabur.app | app | PRIVATE | HTTP 404 | 52.223.32.133 | US | — | 2026-08-26 | Unpkg, HTTP/3, Tailwind CSS | 2026-08-15 | TRUE | {"A":["52.223.32.133"]} | 0 | 0 | — | — | — | — | — | — | — | — |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … |
Visualizzazione 5 di 355 righe · All active domains · Ogni dominio attivo con il relativo TLD e tipo di dominio.
Il dataset .zeabur.app
Tutto ciò che abbiamo su 355 domini .zeabur.app in un unico file scaricabile, con un’esportazione aggiornata ogni giorno. Stesse colonne e stessa cadenza di qualsiasi TLD di primo livello.
Acquistare un dataset per scaricare .zeabur.app
Il frammento completo di .zeabur.app (JSONL, esportazioni giornaliere aggiornate) si trova all’interno di ogni dataset. Lo ottenga da €29 a €599 al mese e lo scarichi subito.
Come scaricare la lista dei domini .zeabur.app
La lista completa dei domini .zeabur.app è disponibile come un unico file strutturato. Ogni voce dell’elenco è un singolo dominio registrato, esportato con il suo record completo, così può elaborare tutto offline invece di doverlo scansionare personalmente.
Scelga il dataset adatto al suo caso d’uso, poi scarichi la lista .zeabur.app in JSONL (compressa con zstd), esattamente la stessa lista che alimenta la nostra API. Un campione gratuito della lista è disponibile prima di pagare, e può riscaricare l’ultimo export in qualsiasi momento durante il suo mese di accesso.
Ogni lista .zeabur.app include, per ogni dominio:
- Record DNS, RDAP e WHOIS, registrar e date su tutta la lista.
- Tecnologie rilevate per ogni sito della lista.
- IP di hosting, paese e ranking PageRank / Harmonic.
- Un’esportazione aggiornata ogni giorno, così la lista che riceve non è mai obsoleta.
Domande frequenti
Quanti domini .zeabur.app esistono?
webatla monitora 355 domini .zeabur.app attivi, riesportati ogni giorno, ciascuno con il proprio DNS, RDAP/WHOIS, tecnologie rilevate, IP, paese di hosting e ranking.
Posso scaricare l’elenco completo dei domini .zeabur.app?
Sì, l’elenco completo di .zeabur.app si scarica come JSONL strutturato (zstd). Prima è disponibile un campione gratuito.
Cosa è incluso per ogni dominio, e quanto è aggiornato?
Ogni dominio include lo schema completo (DNS, RDAP/WHOIS, tecnologie, IP e paese, PageRank e Harmonic), riesportato ogni giorno.
Come scarico l’elenco dei domini .zeabur.app?
Scelga un dataset, e l’elenco completo di .zeabur.app sarà suo come un unico file JSONL nel suo account. Può riscaricare l’elenco in qualsiasi momento durante il suo mese di accesso, e un campione gratuito è disponibile da scaricare prima.
In che formato è disponibile l’elenco .zeabur.app?
L’elenco è suo da scaricare come JSONL compresso con zstd, un dominio per riga, pronto da caricare direttamente in qualsiasi database o script. Lo stesso identico elenco è raggiungibile anche tramite la nostra API.
Posso scaricare solo i domini .zeabur.app, o l’intero database?
Entrambe le opzioni. Ogni dataset è un singolo file scaricabile, ne acquisti solo quello che le serve per .zeabur.app. Oppure acquisti il dataset All data per l’intero database: tutti i dataset combinati (identità, ranking, tecnologie, DNS e RDAP/WHOIS) in un unico file. Esportazione giornaliera aggiornata.
Ottenga l’elenco completo dei domini .zeabur.app
Scelga il dataset che copre ciò di cui ha bisogno. Ciascuno include .zeabur.app ed è scaricabile in JSONL, ricostruito ogni giorno.
All active domains
4 colonne
Ogni dominio attivo con il relativo TLD e tipo di dominio.
€29 / mese
Acquistare e scaricare →
Websites + Ranking
9 colonne
Siti attivi con paese, PageRank, rango armonico e date del dominio.
€99 / mese
Acquistare e scaricare →
Technologies
14 colonne
Lo stack tecnologico completo di ogni sito: CMS, pagamenti, analytics, framework.
€159 / mese
Acquistare e scaricare →
DNS
7 colonne
Record DNS completi per ogni dominio su 21 tipi di record, con stato di risoluzione e dati per singolo record, esportati ogni giorno.
€199 / mese
Acquistare e scaricare →
RDAP & WHOIS
9 colonne
Registrar, intestatario, cronologia di registrazione e record RDAP e WHOIS.
€299 / mese
Acquistare e scaricare →
All data
23 colonne
Tutto quello che abbiamo, in un unico pacchetto. L’universo webatla completo.
€599 / mese
Acquistare e scaricare →
Vuole confrontare tutti i dataset fianco a fianco? Visitare la pagina dei prezzi
Altri suffissi sotto