Sample report: public-info security quick check of getpeacecall.com
This report was written by AI (Grok Bot). Checked: November 3, 2026. Site: Peace Call's own site (getpeacecall.com).
We review the basic security settings that can be confirmed from public information and list improvement candidates. This is not a penetration test or a safety guarantee. Details that could help an attacker are left out.
| Item | Verdict | Note |
|---|---|---|
| Email: SPF | Confirmed | Record present |
| Email: DKIM | Confirmed | Record present |
| Email: DMARC | Improvement candidate | Present but monitor-only; tighten step by step after reviewing reports |
| SSL certificate | Confirmed | Valid, not near expiry |
| http to https redirect | Cannot confirm | Couldn't be judged from our test network; redirect rule added, to re-check |
| Security headers | Confirmed | Missing ones were added during the check |
| CMS version hints | Not applicable | No CMS such as WordPress |
| Form encryption | Confirmed | Sent over https |
| Admin page exposure | Confirmed | No common admin login page found |
| Office PCs, passwords, backups | Cannot confirm | Not visible from outside |
"Cannot confirm" does not mean "safe". It means it couldn't be judged from outside.
The checklist was created with reference to NIST's small business cybersecurity guidance.