Explorer
Syncing—

URL Phishing ReputationService

url-phishing-reputation

Phishing and malicious-URL reputation check. POST JSON {"url": "https://..."} to /v1/reputation; the URL itself is not fetched. The response is a JSON object with url, host, verdict, heuristics, threat_matches and checked_sources. Verdicts: malicious (a threat database matched), suspicious (URL heuristics fired: raw IP host, punycode host, user@host, credential words in the host, very long host, deep subdomains), clean (a threat database was checked and found nothing) and unknown (no threat database was consulted and no heuristic fired). This supplier has no threat database configured (Google Safe Browsing is used only when the supplier sets an API key), so answers are suspicious or unknown, never clean. checked_sources shows exactly what ran. Identical input gives identical output while no threat database is configured.

Active Suppliers
2
of 2 ever configured
Service Info
Service ID
url-phishing-reputation
Compute Units / Relay
100,000
Owner
pokt15…a5px
Active Applications
2
Relay Mining EMA
1 relays
Service Metadata Cardsource: on-chain metadata (LCD)
{10 items
"schema":"pocket-service-card/v1"
"description":"Phishing and malicious-URL reputation check. POST JSON {"url": "https://..."} to /v1/reputation; the URL itself is not fetched. The response is a JSON object wi..."
"rpc_types":[1 item
0:{4 items
"type":"REST"
"intent":"expected"
"backend_hint":"url-phishing-reputation HTTP server on :8080; POST /v1/reputation (also POST /v1/tool), GET /v1/health + /v1/version."
"notes":"Every response is a JSON object; errors are JSON 4xx with an error field."
}
]
"apis":[1 item
0:"url-reputation-api"
]
"specs":[1 item
0:{4 items
"kind":"openapi"
"api":"url-reputation-api"
"url":"https://main.aristeon.org/url-phishing-reputation/openapi.json"
"notes":"Machine-readable OpenAPI 3.0.3 contract for this service, with example requests."
}
]
"access":"public"
"results":"variable"
"serving":{7 items
"backend":"Single-process Python 3 HTTP server, standard library only, behind a RelayMiner (rest backend). URL heuristics run locally. If the supplier sets GOOGLE_SAFE_BRO..."
"implementations":[1 item
0:"url-phishing-reputation >= 1.0"
]
"docs":"https://main.aristeon.org/url-phishing-reputation/README.md"
"min_disk_gb":1
"min_ram_gb":1
"healthcheck":[3 items
0:{4 items
"rpc_type":"REST"
"request":{2 items
"path":"/v1/version"
"method":"GET"
}
"expect":{2 items
"json_path":"$.service"
"matches":"^url-phishing-reputation$"
}
"notes":"Identity probe: pins the backend to this service so a wrong backend cannot be staked under this id."
}
1:{4 items
"rpc_type":"REST"
"request":{2 items
"path":"/v1/health"
"method":"GET"
}
"expect":{2 items
"json_path":"$.status"
"matches":"^ok$"
}
"notes":"Readiness probe."
}
2:{4 items
"rpc_type":"REST"
"request":{3 items
"path":"/v1/reputation"
"method":"POST"
"body":{1 item
"url":"http://192.0.2.1/login"
}
}
"expect":{2 items
"json_path":"$.verdict"
"matches":"^suspicious$"
}
"notes":"Functional probe: a raw-IP login URL must be flagged suspicious. No upstream calls unless a threat database is configured."
}
]
"notes":"Upstream: none by default. Google Safe Browsing only with a supplier API key; check Google terms for commercial use. Gateway operators: configure as type passth..."
}
"docs":"https://main.aristeon.org/url-phishing-reputation/README.md"
"updated":"2026-09-29"
}