Domain Age Checker
Pricing
from $1.13 / 1,000 domain checkeds
Domain Age Checker
Domain Age Checker returns normalized, review-ready API data with robust inputs, consistent outputs, and pay-per-result pricing.
Pricing
from $1.13 / 1,000 domain checkeds
Rating
0.0
(0)
Developer
Virtual Footprint LLC
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Domain Age & WHOIS Checker
Look up domain registration data via RDAP — the IETF-standardized successor to WHOIS. Structured JSON, no scraping, no API key. Get registrar, creation date, expiration date, computed domain age, nameservers, and status codes for any domain, in bulk.
Pricing: $0.0001 one-time actor-start + $0.003 per domain successfully resolved. Domains that don't resolve (never registered, or the TLD's registry doesn't support RDAP) are never charged.
Why RDAP instead of scraping WHOIS pages
Legacy WHOIS is unstructured plain text with a different format per registry, and many registries now redact WHOIS output. RDAP replaced it as the IETF standard (RFC 7480+): every registry publishes RDAP as clean, structured JSON, no rate-limit-prone scraping needed. This actor queries rdap.org, a public RDAP bootstrap service that resolves the correct authoritative registry server per TLD.
Input
| Field | Type | Required | Description |
|---|---|---|---|
domains | array<string> | one of domains/domain | Domains to check. Bare domains or full URLs both work. |
domain | string | one of domains/domain | Single-domain convenience alternative. |
Output (per domain)
{"domain": "google.com","found": true,"registrar": "MarkMonitor Inc.","createdDate": "1997-09-15T04:00:00Z","expiresDate": "2028-09-14T04:00:00Z","ageDays": 10559,"ageYears": 28.9,"nameservers": ["NS1.GOOGLE.COM", "NS2.GOOGLE.COM"],"status": ["client delete prohibited", "client transfer prohibited"],"reason": null,"checkedAt": "2026-08-13T17:24:00Z"}
Domains that don't resolve return found: false with a reason (not_found_or_unregistered, unsupported_tld, network_error, etc.) — never a fabricated result.
What this doesn't do
No legacy-WHOIS plain-text parsing (RDAP coverage is now near-universal across gTLDs and most ccTLDs, but a handful of smaller ccTLD registries haven't adopted RDAP yet — those return unsupported_tld, not a guess).