{
"ok": true,
"data": {
"domain": "github.com",
"risk_score": 0,
"brand_safety_score": 100,
"grade": "A",
"summary": "Low risk. No major fraud signals were detected from public DNS, certificate, and registration data.",
"factors": [
{
"signal": "domain_age",
"points": -15,
"severity": "positive",
"detail": "Domain has been registered for 6982 days."
},
{
"signal": "ssl",
"points": -12,
"severity": "positive",
"detail": "Certificate is valid for 67 more days (Sectigo Public Server Authentication CA DV E36)."
},
{
"signal": "spf",
"points": -6,
"severity": "positive",
"detail": "SPF is present and restrictive."
},
{
"signal": "dmarc",
"points": -8,
"severity": "positive",
"detail": "DMARC policy is quarantine or reject."
},
{
"signal": "dkim",
"points": -3,
"severity": "positive",
"detail": "A common DKIM selector published a key."
},
{
"signal": "blocklist",
"points": 0,
"severity": "info",
"detail": "Spamhaus DBL refused the lookup from this resolver."
}
],
"signals": {
"domain_age_days": 6982,
"registered": "2007-10-09T18:20:50Z",
"registrar": "MarkMonitor Inc.",
"ssl_valid": true,
"ssl_days_remaining": 67,
"ssl_issuer": "Sectigo Public Server Authentication CA DV E36",
"spf": "v=spf1 ip4:192.30.252.0/22 include:spf.protection.outlook.com include:_netblocks.google.com include:_netblocks2.google.com include:mail.zendesk.com include:_spf.salesforce.com include:servers.mcsv.net include:mktomail.com include:sendgrid.net ip4:62.253.227.114 ip4:166.78.69.169 ip4:166.78.69.170 ip4:166.78.71.131 ~all",
"dmarc": "v=DMARC1; p=quarantine; sp=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1",
"dkim_found": true,
"mx_provider": "Microsoft 365",
"typosquat": null,
"blocklist": {
"listed": null,
"source": "spamhaus_dbl",
"status": "blocked",
"return_code": "127.255.255.254"
},
"hosting": {
"ip": "140.82.113.3",
"asn": null,
"asn_name": "GITHU",
"provider": "GITHU",
"country": "US",
"prefix": "140.82.112.0-140.82.127.255"
},
"title": "GitHub · Change is constant. GitHub keeps you ahead. · GitHub",
"reachable": true
}
},
"meta": {
"request_id": "fa034b88f68d4840afde922f823076a1",
"api": "website-risk",
"version": "1",
"elapsed_ms": 12793,
"llm_used": false,
"cache_hit": false,
"warnings": [
"blocklist_blocked"
],
"plan": null
}
}
curl --location --request GET 'https://zylalabs.com/api/15179/website+risk+score+api/40584/score+get?domain=github.com' --header 'Authorization: Bearer YOUR_API_KEY'
{
"ok": true,
"data": {
"domain": "github.com",
"risk_score": 0,
"brand_safety_score": 100,
"grade": "A",
"summary": "Low risk. No major fraud signals were detected from public DNS, certificate, and registration data.",
"factors": [
{
"signal": "domain_age",
"points": -15,
"severity": "positive",
"detail": "Domain has been registered for 6982 days."
},
{
"signal": "ssl",
"points": -12,
"severity": "positive",
"detail": "Certificate is valid for 67 more days (Sectigo Public Server Authentication CA DV E36)."
},
{
"signal": "spf",
"points": -6,
"severity": "positive",
"detail": "SPF is present and restrictive."
},
{
"signal": "dmarc",
"points": -8,
"severity": "positive",
"detail": "DMARC policy is quarantine or reject."
},
{
"signal": "dkim",
"points": -3,
"severity": "positive",
"detail": "A common DKIM selector published a key."
},
{
"signal": "blocklist",
"points": 0,
"severity": "info",
"detail": "Spamhaus DBL refused the lookup from this resolver."
}
],
"signals": {
"domain_age_days": 6982,
"registered": "2007-10-09T18:20:50Z",
"registrar": "MarkMonitor Inc.",
"ssl_valid": true,
"ssl_days_remaining": 67,
"ssl_issuer": "Sectigo Public Server Authentication CA DV E36",
"spf": "v=spf1 ip4:192.30.252.0/22 include:spf.protection.outlook.com include:_netblocks.google.com include:_netblocks2.google.com include:mail.zendesk.com include:_spf.salesforce.com include:servers.mcsv.net include:mktomail.com include:sendgrid.net ip4:62.253.227.114 ip4:166.78.69.169 ip4:166.78.69.170 ip4:166.78.71.131 ~all",
"dmarc": "v=DMARC1; p=quarantine; sp=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1",
"dkim_found": true,
"mx_provider": "Microsoft 365",
"typosquat": null,
"blocklist": {
"listed": null,
"source": "spamhaus_dbl",
"status": "blocked",
"return_code": "127.255.255.254"
},
"hosting": {
"ip": "140.82.112.4",
"asn": 36459,
"asn_name": "GITHUB - GitHub, Inc.",
"provider": "GITHUB - GitHub, Inc.",
"country": "US",
"prefix": "140.0.0.0/8"
},
"title": "GitHub · Change is constant. GitHub keeps you ahead. · GitHub",
"reachable": true
}
},
"meta": {
"request_id": "e52e23c991f141e68c804b3b8d370a2f",
"api": "website-risk",
"version": "1",
"elapsed_ms": 0,
"llm_used": false,
"cache_hit": true,
"warnings": [
"blocklist_blocked"
],
"plan": null
}
}
curl --location --request POST 'https://zylalabs.com/api/15179/website+risk+score+api/40585/score+post' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"domain":"github.com"}'
注册后,每个开发者都会被分配一个个人 API 访问密钥,这是一个唯一的字母和数字组合,用于访问我们的 API 端点。要使用 网站风险评分 API 进行身份验证,只需在 Authorization 标头中包含您的 bearer token。
| 标头 | 描述 |
|---|---|
授权
|
必需
应为 Bearer access_key. 订阅后,请查看上方的"您的 API 访问密钥"。
|
根据域名年龄、TLS、SPF、DMARC、托管情况、仿冒域名和黑名单信号,对域名进行欺诈和品牌安全评分
它会返回一个 0-100 的欺诈风险评分、一个相应的品牌安全评分、一个字母等级、一段摘要以及解释该数值的因素列表
来自 RDAP 的域名年龄、TLS 证书有效性、SPF 和 DMARC 策略、常见选择器上的 DKIM、托管 ASN、可疑顶级域、拼音码、域名仿冒、停放页面文案和 Spamhaus DBL 查询
发送 GET /v1/score?domain=example.com,并附上 X-Api-Key 请求头。响应是包含 ok、data 和 meta 字段的 JSON】【。
调用仍然成功。相关因素表明查询被阻止,而不是编造列表
是。使用字母等级或风险评分,在结账、广告审核或合作伙伴入驻流程中进行拦截、审核或加强验证。因素列表显示了评分的原因
向 POST score 端点发送一个 JSON 请求,并在请求正文中包含域名。请使用完全限定域名,例如 `github.com`。该端点评估提交的域名,并返回与 GET 端点相同的评分数据。
两个端点都会对一个域名进行评分并返回相同的结果。GET 将域名作为查询参数接收,例如 `/v1/score?domain=example.com`;POST 则在 JSON 请求体中接收域名。对于简单的基于 URL 的请求,请选择 GET;发送结构化请求数据时,请选择 POST
`risk_score` 是一个归一化的欺诈风险值,范围为 0 到 100。数值越低,表示检测到的欺诈信号越少;数值越高,表示风险越令人担忧。例如,`risk_score: 0` 的响应代表观测到的最低风险等级。 .
`grade` 提供简洁的字母分类,例如 `A`。`summary` 提供易于理解的整体结果说明,例如指出未检测到重大欺诈信号。使用 grade 快速做出决策,使用 summary 作为展示或审核背景信息】【。
`factors` 中的每一项都标识一个信号、其在 `points` 中的分数贡献、一个 `severity` 分类,以及一条描述性 `detail` 消息。例如,`domain_age` 因素可以说明注册时长,而 `ssl` 因素可以描述证书的有效性
因子分值显示单项信号如何影响评估。负分通常代表令人安心的证据,例如已建立的域名或有效的 TLS 证书。`severity` 字段和 `detail` 文本提供预期的解读;最终决策应使用汇总分数】【。
成功的响应是包含 `ok` 字段和 `data` 对象的 JSON。`data` 对象包含提交的 `domain`、`risk_score`、`brand_safety_score`、`grade`、`summary` 和 `factors` 数组。客户端应先检查 `ok`,再处理评分字段