Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/4 IPs match cert SANREVIEW
BHTTP Probe TimingTotal 1482 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations33 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records2 A records, 74 ms lookupPASS
| A | 172.67.188.187, 104.21.65.30 |
| AAAA | 2606:4700:3031::ac43:bcbb, 2606:4700:3030::6815:411e |
| CNAME | — |
| NS | john.ns.cloudflare.com, love.ns.cloudflare.com |
| MX | 0 norriq-com.mail.protection.outlook.com |
| TXT | 1846d8b67ca52fd5b248b2ffa7a55646 59e521736a066636adb3241501c72553 9BLF9G2pyw4WkNrk/ybaEjZNCescjw3PLsUbhzQJwxi4DwxHC3Y2FxfR6SxccYfk6KKTfAo4iFmWrH4X... Ez5NRvUkyBXeQJz0oBTkpcJLpaVEKqs1KsLN95rs9kUOsmeMC/KZV5YGqMRfDJ1xfU0VaaqFX91uA/F8... _globalsign-domain-verification=br5AyRqJmAhwqmfsiMtBNDn08Z4fxSQZhSRfCMJTfG anthropic-domain-verification-m5gnxf=nhaw6Yh8LeJN2W2mebnnW06R6 globalsign-domain-verification=SPdTwTJKBaqrc85XcKZPCt0iBm_JOz9fl7KeRpHGf1 google-site-verification=6XZSR26fKsAwMaVRDBjzrrACuFhyvEewrya1KS-Dt7Q google-site-verification=8m1NtFf7Qc4V2sM4OiI582HvMDXtXt6qZieQBiAC5eA lNpXqpkmKzU6ppjXV3jFXeE1ITvRxYwhIUfmZwdhL+KowS0skeHOsOPNZAYMMP6WnOqYYgXJ3jktkqid... SPF v=spf1 ip4:87.54.5.98 include:spf.protection.outlook.com include:sendgrid.net in... |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 22ms across 3 resolvers (spread 49ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://norriq.com
696 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://norriq.com | 200 | 696 ms | HTTP/1.1 | cloudflare |
A+Crawlabilityrobots.txt present, sitemap with 1 URLsPASS
# 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 corresponding use.
# The content signals and their meanings are:
# search: building a search index and providing search results (e.g., returning
# hyperlinks and short excerpts from your website's contents). Search does not
# include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
# augmented generation, grounding, or other real-time taking of content for
# generative AI search answers).
# ai-train: training or fine-tuning AI models.
# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.
# BEGIN Cloudflare Managed content
User-agent: *
Content-Signal: search=yes,ai-train=no
Allow: /
User-agent: Amazonbot
Disallow: /
User-agent: Applebot-Extended
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: CloudflareBrowserRenderingCrawler
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: meta-externalagent
Disallow: /
# END Cloudflare Managed Content
User-agent: *
Disallow:
Sitemap: https://norriq.com/api/sitemap/norriq.com/en-US
Sitemap: https://norriq.com/api/sitemap/norriq.dk/da-DK
Sitemap: https://norriq.com/api/sitemap/norriq.dk/en-BE
Sitemap: https://norriq.com/api/sitemap/norriq.dk/nl-BE
Sitemap: https://norriq.com/api/sitemap/norriq.finance/en-BE
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligencenorriq.com — via Key-Systems GmbH, 19 years, 3 months old, hosted on CloudflarePASS
352 days
May 2, 2027
33 days
Issued by Let's Encrypt
19 years, 3 months
Registered May 2, 2007
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS13335
172.67.188.187
Key-Systems GmbH
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice