3things to fix
!DNSSEC not enabled - enable it to prevent DNS spoofing.▸
Turn on DNSSEC at your DNS host, then publish the DS record at your registrar to complete the chain of trust.
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
A208.80.154.224
AAAA2620:0:861:ed1a::1
Nameserversns0.wikimedia.org.
ns1.wikimedia.org.
ns2.wikimedia.org.
MX10 mx-in1001.wikimedia.org.
10 mx-in2001.wikimedia.org.
CAA0 iodef "mailto:dns-admin@wikimedia.org"
0 issue "letsencrypt.org"
0 issue "pki.goog"
SOAns0.wikimedia.org. hostmaster.wikimedia.org. 2026102315 43200 7200 1209600 3600
Mail authentication
SPFv=spf1 include:_cidrs.wikimedia.org ~allPass
DMARCpolicy: p=rejectPass
DKIMnot detected on common selectors-
DNSSEC
ZoneOff
IP intelligence
Primary IP208.80.154.224
Reverse DNStext-lb.eqiad.wikimedia.org.
TLS certificate
CertificateLet's Encrypt · expires 2027-01-02 (53d)Valid
HTTP security headers
HTTPS redirectYes
HSTSYes
CSPNo
X-Content-TypeNo
X-Frame-OptionsNo
Referrer-PolicyNo
Permissions-PolicyNo
Servermw-web.eqiad.main-5f5bf9c477-l4pl9
Add this badge to your site
<a href="https://nattvakt.com/report/wikipedia.org"><img src="https://nattvakt.com/badge/wikipedia.org.svg" alt="Domain health"></a>