ncsc.gov.uk
The National Cyber Security Centre | National Cyber Security Centre
● HTTP 200
→ https://www.ncsc.gov.uk/
🛡 Security Posture — 6/7 checks passing
HTTPS
✓ Yes
HSTS
✓ Yes
SPF
fail
DMARC
✗ No
robots.txt
✓ Yes
security.txt
✓ Yes
sitemap.xml
✓ Yes
🌐 DNS Records
| A | 99.86.12.100 |
| 99.86.12.19 | |
| 99.86.12.24 | |
| 99.86.12.113 | |
| MX | 0 ncsc-gov-uk.mail.protection.outlook.com. |
| NS | ns-1018.awsdns-63.net. |
| ns-1064.awsdns-05.org. | |
| ns-1863.awsdns-40.co.uk. | |
| ns-334.awsdns-41.com. | |
| TXT | "apple-domain-verification=XcjoJFjSHOEl1l0x" (Apple Domain Verification) |
| "atlassian-domain-verification=0YfuEpktsCUA4qzo9up3b7Oc5wMv3wGmMqVsNiuqHY4QKiZ/5AYmSaNLK73IbLLP" (Atlassian Verification) | |
| "d365mktkey=6979ze2417adit18q17fepsqd" | |
| "google-site-verification=fVTp_isR1Kujpthr7JeHpEf5sR7UbOjJ-XOUpngXej8" (Google Site Verification) | |
| "google-site-verification=npZLRIpp2M5JRXldE1y_hOb5X7hnfB-34T8osuxyxXE" (Google Site Verification) | |
| "v=spf1 include:spf.protection.outlook.com -all" (SPF) | |
| "wLOq0jjevbdDkZ/BEbQZhD5jXcdncT4+h2JkY605uzs=" | |
| SOA | ns-1064.awsdns-05.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 |
| CAA | 0 iodef "mailto:infrastructure@ncsc.gov.uk" |
| 0 issue "Digicert.com" | |
| 0 issue "amazon.com" | |
| 0 issue "comodo.com" | |
| 0 issue "globalsign.com" | |
| 0 issue "letsencrypt.org" | |
| 0 issue "pki.goog" |
📋 WHOIS
No WHOIS data available
⚡ HTTP Details
Status 200
Server cloudflare
DNS Host AWS Route 53
Final URL https://www.ncsc.gov.uk/
Content-Type text/html
📧SPF Record — policy: fail
v=spf1 include:spf.protection.outlook.com -all
🔐security.txt
Canonical: https://www.ncsc.gov.uk/.well-known/security.txt
Contact: mailto:security@ncsc.gov.uk
Encryption: https://www.ncsc.gov.uk/sites/default/files/2026-02/ncsc_public_2026-09-11_3446EC55.asc
Expires: 2026-11-09T00:00:00Z
Policy: https://www.ncsc.gov.uk/vulnerability-reporting
Preferred-Languages: en
🤖robots.txt
# As a condition of accessing this website, you agree to abide by the following
# content signals:
# (a) If a Content-Signal = yes, you may collect content for the corresponding
# use.
# (b) If a Content-Signal = no, you may not collect content for the
# corresponding use.
# (c) If the website operator does not include a Content-Signal for a
# corresponding use, the website operator neither grants nor restricts
# permission via Content-Signal with respect to the correspon
Data collected: 21 June 2026