Security snapshot
Across 6 inbusiness-child WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 0%
Grade D 0%
Grade F 100%
Fail the header check (F)100%vs 82.6% avg
Leak usernames33%vs 38.6% avg
Expose a sensitive file16.7%vs 1.8% avg
Use HTTPS83%vs 96.3% avg
What stands out
TLDWP currently associates 6 indexed WordPress sites with inbusiness-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 100% versus 82.6% overall (+17.4 percentage points).
Sensitive-file exposure is 16.7% vs 1.8% overall (+14.9 pp); HTTPS adoption is 83.3% vs 96.3% overall (-13 pp); Username enumeration is 33.3% vs 38.6% overall (-5.3 pp).
These are observational associations among sites where TLDWP detected inbusiness-child, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Version | Exposures | Headers | Last Checked |
|---|---|---|---|---|
| d*b*r*n*.no | 1.0.2· 100% conf. | F | Sep 10, 2026 | |
| v*s*e*.no (WP 7.0.2) | 1.0· 100% conf. | F | Sep 9, 2026 | |
| n*s*i*.no (WP 7.0.4) | — | F | Aug 25, 2026 | |
| n*b*e*r*s*u*s.com (WP 7.0.4) | — | F | Aug 24, 2026 | |
| n*b*e*.no (WP 7.0.4) | — | F | Aug 16, 2026 | |
| s*n*l*n*-*o*v.no (WP 6.1.1) | — | F | Aug 4, 2026 |
Page 1 of 1