API Docs

Check up to 200 domains. Rotates through registrars (Dynadot, NameSilo, Namecheap, Name.com, OpenProvider) and always cross-checks with RDAP. Returns an OR-gate verdict: if any source says "available", verdict = available.

Request

curl -X POST https://dropseer.com/v1/check \
  -H "Content-Type: application/json" \
  -d '{"domains":["aora.in","example.com"]}'

Options

• domains (required) — array of FQDN strings, max 200
• all (optional) — if true, query all registrars in parallel instead of rotating (slower, more accurate)
• source (optional) — force a specific registrar: dynadot / namesilo / namecheap / name.com / openprovider / rdap

Response

{
  "results": [
    {
      "domain": "aora.in",
      "verdict": "available",
      "available": true,
      "sources": [
        {"source": "dynadot", "available": false},
        {"source": "rdap", "available": true}
      ]
    }
  ],
  "sources_used": ["dynadot", "rdap"],
  "took_ms": 1280
}

Given up to 100 domains, run WHOIS, apply per-TLD lifecycle rules (auto-renew grace + RGP + pendingDelete), and return predicted drop date with confidence.

Takes ~3-8s per domain on first call; results cached 24h.

Request

curl -X POST https://dropseer.com/v1/predict \
  -H "Content-Type: application/json" \
  -d '{"domains":["example.com","yourbrand.in"]}'

Response

{
  "results": [
    {
      "domain": "example.com",
      "expiry_date": 1735689600,
      "predicted_drop_at": 1741299600,
      "confidence": "high",
      "method": "whois_lifecycle(com+65d)",
      "status": ["clientTransferProhibited"],
      "registrar": "IANA"
    }
  ],
  "took_ms": 4230
}

Confidence levels

• high — expiry date is >30 days in the future; prediction is within ±5 days
• medium — expired <1 year ago; prediction within ±15 days
• low — expired >1 year ago; WHOIS may be stale
• none — WHOIS failed or no expiry field found

Start monitoring a domain. We poll on the schedule matching the priority you set, and fire a Telegram/webhook alert on state flip.

Request

curl -X POST https://dropseer.com/v1/watch \
  -H "Content-Type: application/json" \
  -d '{
    "domain": "aora.in",
    "priority": 7,
    "telegram_chat_id": "436019661",
    "min_confirmations": 2
  }'

Fields

• domain (required)
• priority 1-10 — see intervals below
• expected_drop_at — UNIX ts; optional; used for adaptive polling near T-0
• callback_url — webhook POST'd on state flip
• telegram_chat_id — chat to notify (register it first via bot)
• min_confirmations — require N sources to agree before firing alert (default 1)

Priority → poll interval

• 1-3 casual → 6h
• 4-6 default → 90s
• 7-8 hot → 30s
• 9 critical → 5s
• 10 dropcatch → adaptive (1s-500ms near T-0)

curl https://dropseer.com/v1/watch

curl -X DELETE https://dropseer.com/v1/watch/aora.in

Returns watch config plus last 100 check events.