Domain age and legitimacy
How old and legit is this domain? WHOIS registration, DNS resolution, and TLS certificate in one pass.
3 tools run server-side in one request. You pay once, settle once, and get a single response - no orchestration, no per-step payments, and a partial-success envelope if any step fails. USDC over x402 on any supported chain.
When to use this pack
An agent evaluating a website's trustworthiness needs the basic legitimacy signals: how old is the registration (new domains are higher risk), does it resolve to a real IP, and is the TLS cert valid? Useful for fraud detection, link safety checks, and vendor due diligence.
Tools in this pack
All 3 run inside the single $0.008 call above. Each is also callable on its own if you only need one part.
- Domain WHOIS (RDAP) POST /api/whois Domain registration data via RDAP (the structured WHOIS successor): registrar, creation/expiry dates, status, nameservers.
- DNS lookup POST /api/dns-lookup Resolve any DNS record type for a host: A, AAAA, MX, TXT, CNAME, NS, SOA, CAA, SRV, PTR. Returns the records plus a count. Built on Node's native resolver - no external API.
- TLS certificate POST /api/tls-cert Inspect the TLS certificate of any public host: subject, issuer, validity window, days remaining, SANs, and SHA-256 fingerprint.
Bought one at a time, these 3 tools cost $0.008 together; the pack is that sum less a 10% bundle discount, rounded up to the $0.001 settlement floor, which is $0.008.
Workflow
- Call whois to get registration date, registrar, expiry, and age - domains less than 6 months old are higher risk.
- Call dns-lookup with host=domain and type='A' to verify the domain resolves to a real IP address.
- Call tls-cert with host=domain to check the certificate issuer, validity period, and chain trust.
Arguments
| Name | Required | Description | Example |
|---|---|---|---|
domain | yes | Domain to check (e.g. google.com) | google.com |
What one call returns
A JSON object with pack, args, steps, summary; steps holds one entry per tool (whois, dns-lookup, tls-cert), each with its own result or error. Full example on the API page.
Call it directly
Any x402 client pays the 402 and gets the whole workflow back in one response. With the agent402-client SDK (npm i agent402-client, an ES module):
import { Agent402 } from "agent402-client";
// payFetch: an x402-wrapped fetch your wallet signs (@x402/fetch).
// Tools on the free tier need no options: new Agent402() pays them by proof-of-work.
// an existing prepaid credits key also works: new Agent402({ creditsKey })
const client = new Agent402({ fetch: payFetch });
const result = await client.call("skill-domain-age", {"domain":"google.com"});
Run it in Claude
claude mcp add agent402 -s user -- npx -y agent402-mcp@latest
Then paste this prompt into Claude:
Check the age and legitimacy of google.com using Agent402's domain-age skill pack: (1) whois for registration age and registrar, (2) dns-lookup for A record resolution, (3) tls-cert for certificate validity. Report a trust assessment based on age, DNS health, and cert status.