A freshly registered domain is a fact about a calendar day, not a reason to block a merchant or a user. IP99 publishes that fact on a daily pipeline: GET /v1/domain/registered/{date} returns names registered on a given date, with the landing IP, the registrar, and a country string. Official docs: this feed is updated daily and does not inherit the snapshot cutoff of the passive DNS corpus — do not read corpus_last_seen onto it. Domain data here are observations, not verdicts. JSON samples were verified on 20 November 2026 UTC, using the free, no-key trial. Notes: IP99, domain intel, API, Certificate Transparency.
One curl, one calendar day
curl https://ip99.com/v1/domain/registered/2026-11-19
No API key, no registration. The date must be a real calendar day in YYYY-MM-DD. Verified 20 November 2026 UTC, the call returned HTTP 200 with count 1000 and elapsed_ms 210.7. A shortened sample of the first rows:
{
"count": 1000,
"elapsed_ms": 210.7,
"data": [
{"country": "Hong Kong", "domain": "0-04.cn", "ip": "67.211.78.196", "registrar": "Dimension Network & Communication Limited"},
{"country": "United Arab Emirates", "domain": "0-0mind.com", "ip": "185.158.133.1", "registrar": "Cloudflare, Inc."},
{"country": "", "domain": "0-1.net.cn", "ip": "172.67.182.4", "registrar": "Cloudflare, Inc."},
{"country": "Hungary", "domain": "0-100.hu", "ip": "91.227.139.235", "registrar": "Rackhost Zrt."},
{"country": "Germany", "domain": "0-8-1-1.com", "ip": "217.160.0.21", "registrar": "IONOS SE"}
]
}
Each row has four fields: domain, ip, registrar, and country. Official docs: this endpoint does not paginate. It answers with the first 1,000 rows, sorted by domain name. Passing ?offset= returns HTTP 400 pagination_unsupported. There is no has_more and no next_offset — do not write a loop that looks for them. An empty data array is an answer, not an error: a date with nothing in the feed (verified the same day for 2026-12-01) returns count 0. A non-date such as 2026-13-45 is HTTP 400 invalid_date, not a silent empty list. Branch on error.code, not on error.message.
The 1,000-row cap matters for statistics. Because the slice is alphabetical, the first 1,000 names on 19 November 2026 are dominated by names that sort early — short, numeric, and many .cn labels. That composition describes the first page, not the whole day. Do not turn it into a "most new domains are .cn" headline.
A daily feed, not the pDNS snapshot
Passive DNS on IP99 is a periodically imported corpus. Official guidance: last_seen is a snapshot date, and corpus_last_seen is the cutoff you must read with it; a date that looks a month old does not mean the name went offline. A lookup of ip99.com on 20 November 2026 UTC still showed corpus_last_seen 2026-08-15. The registered-domain feed is a different pipeline. Official docs: it is updated daily and is not bound by that cutoff; do not reuse the same time interpretation.
The trial allowance is also separate from IP lookup: 10 calls per public IP per day, shared across the domain endpoints, confirmed in the X-Daily-Limit: 10 response header. The free /v1/ip allowance (500/day anonymous, 5,000/day with a free key) is a different quota.
The landing IP is a starting point, not a home address
A new name often lands on infrastructure that many other names share. In the first 1,000 rows for 19 November 2026, 188.114.97.3 appeared 147 times and 188.114.96.3 appeared 144 times. A free lookup of the first address the same day (computed_at 2026-11-20T13:12:20Z):
curl https://ip99.com/v1/ip/188.114.97.3
{
"ip": "188.114.97.3",
"computed_at": "2026-11-20T13:12:20Z",
"evidence_state": "none",
"geo": { "continent": "NA", "country": "US", "region": "Indiana", "city": "Francisco", "district": "", "lat": 38.33329, "lon": -87.44708, "tz": "America/Chicago" },
"network": { "asn": 13335, "usage_type": "CDN" },
"risk": { "score": 0, "level": "none", "signals": ["hosting"] }
}
AS13335 and usage_type: "CDN" describe a content network, not a registrant. hosting is a network attribute, not a fraud verdict — official guidance is not to block on hosting or mobile alone. Score 0 with evidence_state: "none" means IP99 holds no current risk evidence, not that the address is safe. risk.score is the freshness and strength of verifiable evidence, not attacker probability. The city is the geolocation of a block (here, Francisco, Indiana); it is not where a person registered a name, and it is not a street address.
The same pattern holds for a single Cloudflare-backed row. 0-1.net.cn came back with an empty country and landing IP 172.67.182.4. The IP lookup (computed_at 2026-11-20T13:12:22Z) returned San Francisco, US, AS13335, CDN, hosting, score 0 / none. An empty country on the registration row is a value, not a failed request. Always look the landing IP up with /v1/ip if you need geo, ASN, usage type, or risk; do not assume the registration country string is the same as geo.country.
Two non-CDN rows, verified the same day, are more ordinary hosting exits:
curl https://ip99.com/v1/ip/91.227.139.235
curl https://ip99.com/v1/ip/217.160.0.21
0-100.hu (91.227.139.235, Rackhost Zrt., country Hungary) resolved to Szeged, HU, AS210579, IDC, hosting, score 0 / none (computed_at 2026-11-20T13:11:11Z). 0-8-1-1.com (217.160.0.21, IONOS SE, country Germany) resolved to Frankfurt am Main, DE, AS8560, IDC, hosting, score 0 / none (computed_at 2026-11-20T13:11:15Z). Still not "the registrant lives there," and still not a reason to hard-ban an account that later appears from a different address.
A window, then a second source
Official guidance on domain intel is to treat "registered today" as an early window, not as guilt. The interesting set is the intersection with "a certificate was issued today": names being stood up before they have victims. Certificate Transparency is a separate call (GET /v1/domain/certs/{domain} or the CT page). Passive DNS (GET /v1/domain/dns/{domain}) and reverse lookup (GET /v1/domain/reverse/{ip}) then tell you where the name has resolved and what else has shared that address — remembering that pDNS is a snapshot corpus with its own cutoff. A malware-list check (GET /v1/domain/malware/{domain}) is a lighter read of the same listing data as the DNS profile; HTTP 200 is returned whether the name is listed or not — branch on whether data is empty.
None of those calls, including this one, return registrant WHOIS. Official docs: IP99 does not hold registrant data (whois is always null on the DNS profile). A new name on a CDN IP is a starting point for pivoting, not a person you can locate.
If you automate this, keep the limits in mind: 10 trial calls a day, first 1,000 names only, empty arrays as valid answers, and the IP risk profile as a separate lookup with its own quota. Add a step-up check when a brand-new name and a fresh certificate line up; do not auto-ban every name that was registered that day.
Try it
curl https://ip99.com/v1/domain/registered/2026-11-19
curl https://ip99.com/v1/ip/188.114.97.3
curl https://ip99.com/v1/ip/172.67.182.4
curl https://ip99.com/v1/ip/91.227.139.235
curl https://ip99.com/v1/ip/217.160.0.21
curl https://ip99.com/v1/me
The domain trial is 10 calls/day per client IP, shared across the domain endpoints and counted separately from IP lookup. Anonymous IP lookup is 500/day per client IP (60/min); a free key raises that to 5,000/day. Check remaining IP-lookup quota with GET https://ip99.com/v1/me. Domain trial endpoints are documented on domain intel and the API reference; they are not in the IP-lookup OpenAPI file. Pricing: https://ip99.com/en/pricing.
Do not treat IP99 scores or geo as identical to other ThreatHunter datasets. This article only claims what the free domain endpoints, free /v1/ip, and the cited product pages document.
IP99 is a ThreatHunter product. A date of registration is a window on a name, not a verdict on a person. Start at https://ip99.com; the domain endpoints are documented on domain intel and https://ip99.com/api.
Top comments (0)