Feature docs · Network & infrastructure
Your brand’s external surface is more than a web page. DNS, email authentication, CDN/WAF, misconfigured cloud storage, and client-side Firebase config also carry risk.
Modules covered
- Open ports: limited signals for sensitive ports such as SSH/DB/cache (not a full port scan)
- WAF / CDN detection: Cloudflare, Akamai, Fastly, CloudFront, and similar layers
- Cloud storage exposure: listability / public access signals on S3, GCS, Azure, R2 URLs
- Firebase config: client config and open database URL signals
- DNS & email: SPF, DKIM, DMARC, DNSSEC — see DNS and email security
- Subdomain takeover: dangling CNAME / claimable hosting risk
Business impact
A public bucket can damage reputation and customer data in one incident. Missing WAF/CDN is not automatically an open door, but it clarifies whether an edge layer is visible. Dangling subdomains remain a classic brand-spoofing vector.
What to do next
- Treat public cloud storage findings as urgent
- Align SPF/DKIM/DMARC correctly
- Clean unused subdomain DNS records
- Keep sensitive ports off the public internet
Run these checks with Guardbee
Add your brand, pick the modules that matter, and get findings in business language. Start with a 14-day free trial.
Frequently asked questions
Is this a full port scan?
No. Guardbee checks limited sensitive-port signals — not aggressive or destructive scanning.
Does no WAF mean insecure?
Not by itself. Detection shows edge-layer visibility and should be read with other findings.
What does a Firebase finding mean?
Visible client config or open DB URL signals. Validate real access policies separately.