Technical Source Validation
To maintain the integrity of the brand ecosystem, all digital touchpoints must be validated against our central security registry. Use the following technical standards to verify the authenticity of a domain or service.
SSL/TLS Certificate Verification
Official properties utilize Extended Validation (EV) or Organization Validated (OV) certificates. Verify the following fingerprints for the primary infrastructure:
Primary Domain: bankonbet.com
Issuer: DigiCert Global Root G2
SHA-256 Fingerprint: 74:2C:BA:F1:C2:3F:4A:5D:6E:7F:8A:9B:0C:1D:2E:3F:4A:5B:6C:7D
DNS Record Authentication
Authorized domains must contain specific TXT records for brand verification. Any domain claiming affiliation without these records should be flagged.
| Record Type | Expected Value Pattern | Purpose |
|---|---|---|
| TXT | v=bob-integrity-v1; id=ASSET_ID | Brand Ownership Verification |
| SPF | v=spf1 include:_spf.bankonbet.com ~all | Email Source Authentication |
| DMARC | v=DMARC1; p=reject; rua=mailto:abuse@... | Anti-Spoofing Policy |
Validation Workflow
01. Protocol Check
Ensure the connection is established over TLS 1.3. Legacy protocols (TLS 1.0/1.1) are deprecated and not used by official assets.
02. Header Analysis
Check for 'X-Brand-Integrity-ID' in the HTTP response headers. Official nodes always broadcast a unique node identifier.
03. Asset Hash
Compare static assets (JS/CSS) against the Asset Registry hashes to ensure no code injection has occurred.