generated: '2026-09-05' method: searched source: https://www.contify.com/news-api/ supporting_sources: - https://www.contify.com/ - https://www.contify.com/privacy-policy/ - https://api.contify.com/v4.1/updates note: >- Contify publishes no OpenAPI, so nothing here is derived from a spec. Compliance claims are quoted from Contify's own pages; protocol conformance was established by live probe or by the absence of any published surface. Contify's market — market and competitive intelligence / business news syndication — has no domain interchange standard in scoring.yml, so no domain_standard entry is asserted. Reward-only: an absent domain standard is not a defect. compliance: published: true page: https://www.contify.com/news-api/ certifications: - id: soc2 name: SOC 2 claimed: true evidence: >- "SOC 2 & GDPR compliant — SOC 2 certified and GDPR compliant, ensuring enterprise-grade data security, privacy, and compliance." — https://www.contify.com/news-api/ badge: https://www.contify.com/wp-content/uploads/2026/02/aicpa-soc-contify.webp type_stated: false report_available: false note: >- The AICPA SOC badge appears in the site footer on every page. Contify does not state SOC 2 Type I vs Type II and publishes no report-request or trust-centre page. - id: iso-27001 name: ISO/IEC 27001 claimed: true evidence: >- Footer certification badge with the tooltip "ISO 27001" (https://www.contify.com/wp-content/uploads/2026/08/iso.svg), site-wide. certificate_number: null note: No certificate number, registrar or scope statement is published. - id: gdpr name: GDPR claimed: true evidence: >- Footer badge tooltip "GDPR" plus https://www.contify.com/privacy-policy/ , which identifies the controller as Athena Information Solutions Pvt Ltd, the owner of Contify. gaps: - No trust centre. trust.contify.com does not resolve; /trust/, /security/, /compliance/ all 404. - No SOC 2 report request path, no subprocessor list, no pen-test summary published. - No security.txt and no vulnerability disclosure policy on any host. standards: - id: rest conforms: true evidence: >- "Structured RESTful JSON outputs with standard HTTP methods (GET, POST, PUT, DELETE)" — https://www.contify.com/news-api/ - id: openapi conforms: false evidence: >- No OpenAPI/Swagger document at any probed location on www.contify.com, contify.com, developer.contify.com or api.contify.com (all 404, 2026-09-05). - id: asyncapi conforms: false evidence: Webhook delivery is advertised but no AsyncAPI document is published. - id: graphql conforms: false evidence: No /graphql surface is advertised or reachable. - id: oauth2 conforms: false evidence: >- Authentication is a static APPID/APPSECRET header pair; no OAuth 2.0 surface and no /.well-known/oauth-authorization-server (404 on every host). - id: oidc conforms: false evidence: /.well-known/openid-configuration returns 404 on every Contify host. - id: rfc9457-problem-details conforms: false evidence: >- Live errors return the Django REST Framework envelope {"detail": "..."} as application/json, not application/problem+json. Observed on https://api.contify.com/v4.1/updates (403) 2026-09-05. - id: rfc9116-security-txt conforms: false evidence: /.well-known/security.txt returns 404 on all four Contify hosts. - id: rfc8594-sunset-header conforms: false evidence: No deprecation or sunset policy published; no Sunset header documented. - id: idempotency conforms: false evidence: No idempotency key or replay-protection contract is documented. - id: apis-json conforms: false evidence: /apis.json, /apis.yml and /.well-known/apis.json all 404 on every host. - id: llms-txt conforms: true evidence: >- https://www.contify.com/llms.txt returns HTTP 200 with a valid llms.txt document (H1 + sectioned link lists). Saved verbatim at llms/contify-llms.txt. It indexes marketing and blog pages only — no API reference is listed in it. - id: mcp conforms: false evidence: No MCP server is published or advertised. - id: a2a conforms: false evidence: >- /.well-known/agent-card.json and /.well-known/agent.json return 404 on all four Contify hosts. checked: '2026-09-05'