Skip to content
https://regjeringen.no

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
B
Redirect Chain
2 redirect(s), 373 ms total
REVIEW
2 redirect(s), 373 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect

https://regjeringen.no

147 ms · HTTP/1.1

301

https://www.regjeringen.no/

180 ms · HTTP/1.1

301

https://www.regjeringen.no/no/id4/

46 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://regjeringen.no301147 msHTTP/1.1cloudflare
2https://www.regjeringen.no/301180 msHTTP/1.1cloudflare
3https://www.regjeringen.no/no/id4/20046 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
TLS Certificate Expiry & Recommendations
44 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

44
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: EWR)
Got: cf-ray: 9f07babfde547cea-EWR
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f07babfde547cea-EWR
A+
DNS Records
1 A records, 120 ms lookup
PASS
1 A records, 120 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 217.114.94.2
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 120 ms
Got: 120 ms
A217.114.94.2
AAAA
CNAME
NSns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info
MX
TXT
SPF v=spf1 -all
9H53PQV9EGG3TS5E6BKBFFF6TP
5f3d7be6fe588a5ba55b1414d31fde832bd06b32ff95f3adfea8a73093276b19
CAALookup not available with standard resolver
Resolved in 120 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 1069 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1069 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Sitemap: https://www.regjeringen.no/globalassets/sitemap/sitemap.xml
Disallow: /*/?documenttype
Disallow: /*/?topic
Disallow: /*/?ownerid
Disallow: /*/?from
Disallow: /*/?to
Disallow: /*/?government
Disallow: /*/?utid
Disallow: /*/?sesjon
Disallow: /*/?type
Disallow: /*/?law
Disallow: /*/?county
Disallow: /*/?term
Disallow: /*/?sortby
Disallow: /*/?sort
Disallow: /*/?expand
Disallow: /*/?querystring
Disallow: /*/?isfilteropen
Disallow: /*/?pageRef
Disallow: /*/?reg_oss
Disallow: /*/?tema
Disallow: /*/?q
Disallow: /*/?bq
Disallow: /*/?uid
Disallow: /*/?docid
Disallow: /*/?personid
Disallow: /*/?eventId
Disallow: /*.xhtml$
Disallow: /contentassets/*.xml$
Disallow: /globalassets/upload/*.xml$
Disallow: /globalassets/departementene/*.xml$
Disallow: /*/?cedit
Disallow: /*&cedit
Disallow: /Utilities/RSSEngine/*
Disallow: /*/?consterm
Disallow: /api/*
Disallow: /no/api/*
Disallow: /nb/api/*
Disallow: /nn/api/*
Disallow: /se/api/*
Disallow: /en/api/*
Disallow: /no/dokumentarkiv/*
Disallow: /en/historical-archive/*
Disallow: /se/dokumeantavuorka/*

sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.regjeringen.no/
200https://regjeringen.no/

Preferred variant: non-www

HTTP → HTTPS

301http://regjeringen.no/ https://www.regjeringen.no/

Consistent

A+
Domain Intelligence
regjeringen.no — via DEPARTEMENTENES DIGITALISERINGSORGANISASJON (DIO), 20 years, 5 months old, hosted on EPISERVER_AS, SE
PASS
regjeringen.no — via DEPARTEMENTENES DIGITALISERINGSORGANISASJON (DIO), 20 years, 5 months old, hosted on EPISERVER_AS, SE
Info::
DNSSEC is enabled
Info::
Registrar: DEPARTEMENTENES DIGITALISERINGSORGANISASJON (DIO)
Info::
Hosting: EPISERVER_AS, SE
Got: AS30811
Domain expiry

Unknown

SSL certificate

44 days

Issued by Google Trust Services

Domain age

20 years, 5 months

Registered February 27, 2006

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

EPISERVER_AS, SE

ASN AS30811

217.114.94.2

Registrar

DEPARTEMENTENES DIGITALISERINGSORGANISASJON (DIO)

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Registrar DEPARTEMENTENES DIGITALISERINGSORGANISASJON (DIO)
Created February 27, 2006 (20 years, 5 months ago)
Last Updated February 27, 2026
Name Servers ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info
DNSSEC Enabled
Hosting
IP Address 217.114.94.2
ASN AS30811 (EPISERVER_AS, SE)
Provider EPISERVER_AS, SE
Data source: rdap (0.4s)
A+
HTTP Probe Timing
Total 60 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
35 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
11 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
60 ms
Total Time Total request time from DNS lookup through full response.
60 ms

Connection waterfall

DNS Lookup 35 ms TCP Connect 2 ms TLS Handshake 11 ms Server Processing 12 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback