Skip to content
https://www.lyon-industries.no

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 7 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
C
Reverse DNS
Action
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 76.76.21.22: lookup 76.76.21.22: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 66.33.60.129: lookup 66.33.60.129: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
Multi-Resolver DNS Speed
Mean 108ms across 3 resolvers (spread 111ms)
REVIEW
Mean 108ms across 3 resolvers (spread 111ms)
Info::
Google: 69ms
Got: 69ms via 8.8.8.8:53
Info::
Cloudflare: 77ms
Got: 77ms via 1.1.1.1:53
Info::
Quad9: 180ms
Got: 180ms via 9.9.9.9:53
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
83 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A
DNS Records
2 A records, 29 ms lookup
PASS
2 A records, 29 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 76.76.21.22, 66.33.60.129
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: cname.vercel-dns.com
Info::
4 nameserver(s) configured
Got: ns2.vercel-dns-3.com, ns4.vercel-dns-3.com, ns3.vercel-dns-3.com, ns1.vercel-dns-3.com
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 29 ms
Got: 29 ms
A76.76.21.22, 66.33.60.129
AAAA
CNAMEcname.vercel-dns.com
NSns2.vercel-dns-3.com, ns4.vercel-dns-3.com, ns3.vercel-dns-3.com, ns1.vercel-dns-3.com
MX
TXT
CAALookup not available with standard resolver
Resolved in 29 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A
CAA Records
issue: globalsign.com, letsencrypt.org, pki.goog, sectigo.com
PASS
issue: globalsign.com, letsencrypt.org, pki.goog, sectigo.com
Info::
CAA issue tag present — authorized CA(s): globalsign.com, letsencrypt.org, pki.goog, sectigo.com
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.lyon-industries.no

https://www.lyon-industries.no

121 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.lyon-industries.no200121 msHTTP/1.1Vercel
A+
Crawlability
robots.txt present, sitemap with 19 URLs
PASS
robots.txt present, sitemap with 19 URLs
Info::
robots.txt is present
Got: 105 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 19 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 105 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /

Host: https://lyonindustries.com
Sitemap: https://lyonindustries.com/sitemap.xml

A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.lyon-industries.no/
308https://lyon-industries.no/

HTTP → HTTPS

308http://www.lyon-industries.no/ https://www.lyon-industries.no/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
lyon-industries.no — via WEBHUSET AS, 10 months old, hosted on AWS
PASS
lyon-industries.no — via WEBHUSET AS, 10 months old, hosted on AWS
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: WEBHUSET AS
Info::
Hosting: AWS
Got: AS16509
Domain expiry

Unknown

SSL certificate

83 days

Issued by Let's Encrypt

Domain age

10 months

Registered June 23, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

76.76.21.21

Registrar

WEBHUSET AS

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar WEBHUSET AS
Created June 23, 2025 (10 months ago)
Name Servers ns.datacenter.no, ns2.datacenter.no
DNSSEC Not enabled
Hosting
IP Address 76.76.21.21
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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

A+
HTTP Probe Timing
Total 191 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
82 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
58 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
190 ms
Total Time Total request time from DNS lookup through full response.
192 ms

Connection waterfall

DNS Lookup 82 ms TCP Connect 1 ms TLS Handshake 58 ms Server Processing 50 ms Content Transfer 2 ms
A+
CDN & Delivery
Vercel (HIT)
PASS
Vercel (HIT)
Info::
Site is served via Vercel CDN
Got: x-vercel-id: cdg1::lzhtv-1778420003424-b0ec7be91d71
Info::
CDN cache status: HIT
CDN Detected: Vercel
Provider Vercel Cache Status HIT Evidence x-vercel-id: cdg1::lzhtv-1778420003424-b0ec7be91d71
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 2 header(s)
Got: age=47061, x-vercel-cache=HIT
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback