Domain Reputation API

What you get

Check domain reputation across multiple threat intelligence sources.

SynchronousRESTMCPSDKInteractive tool

Choose this product when

Who it is for

Use bounded passive checks to enrich triage and investigation, not to replace authorized testing or human review.

Choose this product when

Choose this for a combined reputation view with evidence, coverage, and unknown results kept visible.

What you get

Check domain reputation across multiple threat intelligence sources.

Endpoints

Review the supported operations, inputs, outputs, execution modes, and response limits before integrating.

GET /v1/reputation View API reference

Credits and authentication

3 Authentication required. Check the operation reference for the exact cost and any per-item pricing.

Example operation

Use documented operations to collect, assess, enrich, verify, compare, protect, or monitor public evidence.

GET /v1/reputation

Query Parameters

Parameter	Type	required
domain	string	required

Response Fields

Field	Type
`domain`	string
`reputation_score`	integer
`grade`	string
`risk_level`	string
`reputation_score_confidence`	string
`grade_capped_by_parking`	boolean
`factors`	object
`factors.age`	object
`factors.dns_security`	object
`factors.ssl_certificate`	object
`factors.hosting`	object
`factors.web_presence`	object
`factors.blacklists`	object
`factors.email_config`	object
`recommendations[]`	object[]
`recommendations[]`	object
`recommendations[].priority`	string
`recommendations[].category`	string
`recommendations[].action`	string
`recommendations[].impact`	string
`evidence_summary`	object
`evidence_summary.checks_performed`	integer
`evidence_summary.cache_status`	string
`evidence_summary.confidence`	string
`evidence_summary.risk_level`	string
`evidence_summary.factor_count`	integer
`evidence_summary.scored_factor_count`	integer
`evidence_summary.passing_factor_count`	integer
`evidence_summary.warning_factor_count`	integer
`evidence_summary.failing_factor_count`	integer
`evidence_summary.lowest_scoring_factors[]`	object[]
`evidence_summary.lowest_scoring_factors[]`	object
`evidence_summary.lowest_scoring_factors[].name`	string
`evidence_summary.lowest_scoring_factors[].score`	number \| null
`evidence_summary.lowest_scoring_factors[].weight`	number \| null
`evidence_summary.blacklist_listed_count`	integer
`evidence_summary.recommendation_count`	integer
`evidence_summary.high_priority_recommendation_count`	integer
`evidence_summary.grade_capped_by_parking`	boolean
`meta`	object
`meta.query_time_ms`	integer
`meta.checks_performed`	integer
`meta.cached`	boolean
`meta.served_by`	string

Example Request

curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/reputation?domain=example.com"

Example Response

{
  "domain": "example.com",
  "reputation_score": 76,
  "grade": "C",
  "risk_level": "medium",
  "reputation_score_confidence": "high",
  "grade_capped_by_parking": true,
  "factors": {
    "age": {
      "score": 84,
      "weight": 0.1,
      "details": {
        "age_days": 5840
      }
    },
    "dns_security": {
      "score": 80,
      "weight": 0.2,
      "details": {
        "dnssec": false,
        "spf": true,
        "dmarc": true,
        "dmarc_policy": "reject"
      }
    },
    "ssl_certificate": {
      "score": 92,
      "weight": 0.2,
      "details": {
        "valid": true,
        "error": null,
        "grade": "A",
        "chain_valid": true,
        "min_tls_version": "TLSv1.3"
      }
    },
    "hosting": {
      "score": 35,
      "weight": 0.1,
      "details": {
        "has_a_records": true,
        "a_record_count": 2,
        "parked": true
      }
    },
    "web_presence": {
      "score": 20,
      "weight": 0.15,
      "details": {
        "has_website": true,
        "redirects_to_https": true,
        "response_time_ms": 87,
        "parked": true,
        "for_sale": false,
        "parking_provider": "Example Parking"
      }
    },
    "blacklists": {
      "score": 100,
      "weight": 0.1,
      "details": {
        "listed": false,
        "threat_level": "none",
        "domain_sources": [],
        "ip_sources": []
      }
    },
    "email_config": {
      "score": 100,
      "weight": 0.15,
      "details": {
        "has_mx": true,
        "has_spf": true,
        "has_dmarc": true,
        "mx_count": 2
      }
    }
  },
  "recommendations": [
    {
      "priority": "high",
      "category": "web_presence",
      "action": "Move the domain off parking if it is intended for customer traffic.",
      "impact": "+10 points"
    }
  ],
  "meta": {
    "query_time_ms": 187,
    "checks_performed": 7,
    "cached": false,
    "served_by": "pop=MAD country=ES"
  }
}

Limits and evidence boundaries

Results describe observed public evidence and its provenance.

Unknown means the requested fact could not be determined from the available evidence.

Coverage is bounded by the documented inputs, budgets, sources, and response limits.

Evidence can change over time; use timestamps and freshness fields when provided.

Reviewed 2026-08-22

Related products

Frequently asked questions

Where can I find the Domain Reputation request and response reference?

Use the API reference for Domain Reputation to review parameters, response fields, examples, status codes, and supported operation modes.

How should I interpret unknown or incomplete results from Domain Reputation?

Unknown or partial results mean that the requested evidence could not be fully determined. Keep the result state, confidence, freshness, and limitations in downstream decisions.

How is Domain Reputation priced?

Pricing depends on the operation and execution mode. Check the endpoint reference for the current credit cost, authentication requirement, and per-item rules.