Domain-Checker-API

#What Domain-Checker solves

A fast way to evaluate if a domain is live, secure, contentful, and legitimate — plus which niche it belongs to. Use it for onboarding checks, partner vetting, SEO audits, ad quality gates, and automated lead scoring.

#Endpoints & when to use them

#POST /v1/domain/check — All-in-one technical check

• Best for: Quick health snapshot (DNS/SSL/HTTP/Meta/Content/WHOIS) with a single call.
• Output: Actionable result plus an evaluation score indicating if the site looks “active”.
• Use cases: Lead qualification, site monitoring, preflight checks before indexing/crawling.

#POST /v1/domain/detect-niche — Practical niche detection

• Best for: Categorizing a site into a single niche (with subniches) for targeting or policy.
• How it works: Uses only page title/description/keywords and domain name (either send HTML, or we fetch a small snippet).
• Output: niche, relevance (0–100), subniches[], and is_sensitive.

#GET/POST /v1/domain/detect-category — Category taxonomy

• Best for: Getting the authoritative list of allowed categories (GENERAL + SENSITIVE) to validate UI or pipelines.
• Output: Flat lists you can present in forms or use to validate classification outputs.

#Quick start

curl -X POST "https://api.yeb.to/v1/domain/check" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: <YOUR_API_KEY>" \
  -d '{
    "domain": "example.com",
    "checks": ["dns","ssl","http","meta","length","whois"],
    "options": { "verbosity": "result", "timeout": 8 }
  }'

curl -X POST "https://api.yeb.to/v1/domain/detect-niche" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: <YOUR_API_KEY>" \
  -d '{ "domain": "popnable.com" }'

#Parameters that actually matter

#/v1/domain/check

#/v1/domain/detect-niche

#/v1/domain/detect-category

#Reading & acting on responses

#/v1/domain/check

{
  "domain": "example.com",
  "timestamp_utc": "2025-10-20T15:11:10Z",
  "result": {
    "ssl":    { "valid": true, "days_left": 72, "valid_to": "2026-01-01T00:00:00Z" },
    "whois":  { "valid_domain": true, "expires_in_days": 180, "created": "2010-05-04", "updated": "2024-11-01",
                "registrar": "Example Registrar", "name_servers_cnt": 2, "name_servers": ["ns1.example.net","ns2.example.net"] },
    "dns":    { "has_host_records": true, "ns_count": 2, "mx_count": 1 },
    "http":   { "status": 200, "final_url": "https://example.com/" },
    "content":{ "thin_content": false, "has_content": true }
  },
  "evaluation": { "active": true, "score": 75 }
}

• First glance: evaluation.active and evaluation.score (0–100) — your quick “is this site healthy?” signal.
• Decisioning tips:
  • Score ≥ 40 → treat as active (crawl, consider for partnerships/ads).
  • No HTTP or expired WHOIS → flag for manual review or block in paid campaigns.
  • content.thin_content = true → avoid indexing or reduce crawl frequency.

#/v1/domain/detect-niche

{
  "data": {
    "niche": "Music",
    "relevance": 97,
    "is_sensitive": false,
    "subniches": [
      {"name":"Celebrities","relevance":84}
    ]
  }
}

• niche — always one of the allowed categories. Use for routing, targeting, or policy.
• is_sensitive — direct compliance helper (ads, affiliate rules, search inclusion).
• relevance — confidence-like score; consider thresholds (e.g., ≥70 accept, else manual check).

#/v1/domain/detect-category

{
  "data": {
    "GENERAL": ["News","Sports","Music","Movies", "..."],
    "SENSITIVE": ["Adult","Casino","Sports Betting","Poker","Lottery", "..."]
  }
}

#Practical recipes

• Lead scoring: If evaluation.active and whois.valid_domain and not content.thin_content → mark as “qualified”.
• Ad safety: If detect-niche.is_sensitive → disallow or route to stricter review queue.
• SEO triage: If http.status ≥ 400 or dns.has_host_records=false → drop from crawl list.

#API Changelog