3things to fix
!No HSTS header - add Strict-Transport-Security.▸
Send Strict-Transport-Security: max-age=31536000; includeSubDomains on every response, at your server or CDN edge.
Read the guide →!No Content-Security-Policy header.▸
Add a Content-Security-Policy. Start in Content-Security-Policy-Report-Only mode, refine it, then enforce.
Read the guide →!Missing X-Content-Type-Options: nosniff.▸
Add the header X-Content-Type-Options: nosniff to stop browsers MIME-sniffing responses.
Read the guide →DNS records
A92.62.118.161
AAAA2a11:4880:0:dfc0::1
Nameserversns1.mijn.host.
ns2.mijn.host.
ns3.mijn.host.
MX10 mx1.mijn.host.
20 mx2.mijn.host.
SOAns1.mijn.host. hostmaster.bedrijfsontruiming.amsterdam. 1757671807 10800 3600 604800 3600
Mail authentication
SPFv=spf1 include:spf.mijn.host ~allPass
DMARCpolicy: p=quarantinePass
DKIMnot detected on common selectors-
DNSSEC
Zone1 DNSKEY record(s)Signed
IP intelligence
Primary IP92.62.118.161
Reverse DNSh49.mijn.host.
TLS certificate
CertificateLet's Encrypt · expires 2026-09-30 (29d)Valid
HTTP security headers
HTTPS redirectYes
HSTSNo
CSPNo
X-Content-TypeNo
X-Frame-OptionsNo
Referrer-PolicyNo
Permissions-PolicyNo
ServerLiteSpeed
Add this badge to your site
<a href="https://nattvakt.com/report/bedrijfsontruiming.amsterdam"><img src="https://nattvakt.com/badge/bedrijfsontruiming.amsterdam.svg" alt="Domain health"></a>