Demo rule: fake domains and seeded results should be clearly labeled as demonstration data. Do not imply the sample companies exist or that the findings are live evidence.
Demo Data Pack
Fake data for convincing product demos.
Use these seeded domains, findings, scores, and UI states to build CyberShield without scanning real third-party domains during early development.
Domains
Seeded CyberShield demo records
Needs improvement
acme-demo.com
Score: 64/100. Missing DMARC enforcement, missing CSP, missing HSTS, SPF too permissive.
Good
bluepeak-demo.io
Score: 88/100. DMARC policy still p=none, missing Permissions-Policy, TLS expires in 32 days.
High risk
novamed-demo.net
Score: 43/100. Expired TLS certificate, no DMARC, no SPF, missing security headers.
Partial scan
northstar-demo.org
Score: 71/100. DNS checks succeeded, HTTPS timed out, mail authentication partially configured.
UI States
Design states the demo should show
Explain what will be checked and ask for authorization confirmation.
Show DNS, website, email, scoring, and report steps without fake precision.
Keep successful evidence visible and label timeouts or unavailable checks clearly.
Show executive summary, top fixes, score breakdown, and technical appendix.
Sample Report Copy
Business-readable output
Executive summary
acme-demo.com has a medium security posture. The highest-impact improvements are enforcing DMARC, adding HSTS, and testing a Content Security Policy.
Top recommendation
Start with email authentication because spoofing risk can affect customers and partners even when the website itself is available.
Caveat
This report checks public configuration evidence. It does not prove whether systems are compromised or whether internal controls are complete.
Recommended use: build the first CyberShield UI against this seeded data, then replace each seed with real passive check output one category at a time.