Guides

Domain allowlist

This document provides a comprehensive list of all domains used by k-ID AgeKit+ and the Compliance Development Kit (CDK). If you are employing a domain allowlist in your security strategy, these domains should be included to ensure your implementation functions properly.

Domain categories

k-ID utilizes various third-party services for different verification methods. Below is a breakdown of domains organized by their purpose:

CategoryDomainPurpose
AgeKey Verification*.agekey.orgSecure age proof stored on a device, used anywhere without sharing personal info.
Facial Age Estimation*.privately.swissPrivacy-preserving facial analysis services
*.faceassure.comFace verification and age estimation
challenges.cloudflare.comCloudflare Turnstile check that confirms a real person is completing the scan, used when Privately is the facial age estimation provider
cdn.jsdelivr.netJavaScript libraries and dependencies
fonts.cdnfonts.comCustom font resources
ID Document Verification*.dcams.appDocument capture and verification services
dcamsclientlogos.s3.us-east-2.amazonaws.comClient branding assets
ConnectID Verification*.connectid.com.auAustralian-owned digital identity solution
KISA Identity Verification*.inicis.comSouth Korea real-name and age verification (KISA-designated methods)
Credit Card Verification*.stripe.comPayment processing and card verification
General Verification Pagesfonts.googleapis.comGoogle Fonts
*.gstatic.comGoogle static content delivery
*.k-id.comCore k-ID services and widgets

Implementation notes

Wildcard domains

Several domains use wildcards (*) to accommodate subdomains. Make sure your allowlist implementation properly supports wildcard matching.

Environment considerations

  • Test Environment: All domains listed are required for both test and production environments
  • Regional Variations: Some services use region-specific subdomains

Troubleshooting

If you experience issues with k-ID widgets:

  1. Check browser developer tools for Content Security Policy (CSP) violations
  2. Ensure all wildcard domains are properly configured
  3. Verify that your CSP syntax is correct
  4. Test in different browsers to ensure compatibility

Security considerations

Warning

Using a domain allowlist is just one approach to securing your application when integrating third-party widgets and services. Modern web security involves multiple layers and strategies. Review the latest security best practices and determine the most appropriate security model for your specific use case and threat model.

While these domains are necessary for developing with the CDK when using a domain allowlist approach, always:

  • Regularly review and update your allowlist configuration
  • Monitor for any unauthorized domain requests
  • Keep your CSP as restrictive as possible
  • Test thoroughly after any CSP changes

Additional resources

For more information about implementing k-ID widgets and CSP configuration:

On this page