Skip to content
https://unpkg.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
7 PASS 2 REVIEW
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.unpkg.com/
200https://unpkg.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://unpkg.com/ https://unpkg.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
A+
DNS Records
2 A records, 31 ms lookup
PASS
2 A records, 31 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.1.22, 104.18.0.22
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:116, 2606:4700::6812:16
Info::
2 nameserver(s) configured
Got: alexia.ns.cloudflare.com, weston.ns.cloudflare.com
Info::
3 mail exchanger(s) configured
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: 31 ms
Got: 31 ms
A104.18.1.22, 104.18.0.22
AAAA2606:4700::6812:116, 2606:4700::6812:16
CNAME
NSalexia.ns.cloudflare.com, weston.ns.cloudflare.com
MX
6 route3.mx.cloudflare.net
36 route2.mx.cloudflare.net
73 route1.mx.cloudflare.net
TXT
SPF v=spf1 include:_spf.mx.cloudflare.net ~all
CAALookup not available with standard resolver
Resolved in 31 ms

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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://unpkg.com

https://unpkg.com

67 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://unpkg.com20067 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:116, 2606:4700::6812:16
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:116, 2606:4700::6812:16 Connection Reachable (17 ms)
A
Crawlability
robots.txt present, sitemap with 0 URLs
PASS
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 733 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 733 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
module.exports = createMiddleware

var readFileSync = require('fs').readFileSync
  , crypto = require('crypto')

function createMiddleware(path, options) {

  // Defaults
  options = options || {}

  if (!path) throw new Error('No path provided for robots.txt file')

  var maxAge = options.maxAge || 86400000
    , txt = readFileSync(path)
    , headers =
      { 'Content-Type': 'text/plain'
      , 'Content-Length': txt.length
      , 'ETag': '"' + crypto.createHash('md5').update(txt).digest('hex') + '"'
      , 'Cache-Control': 'public, max-age=' + (maxAge / 1000)
      }

  return function middleware(req, res, next) {
    if ('/robots.txt' !== req.url) return next()
    res.writeHead(200, headers)
    res.end(txt)
  }

}

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
A+
Domain Intelligence
unpkg.com — via Cloudflare, Inc., 10 years, 5 months old
PASS
unpkg.com — via Cloudflare, Inc., 10 years, 5 months old
Info::
Domain registered until Jan 6, 2027 (8 months remaining)
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: Cloudflare, Inc.
Warning::
Registrar lock is NOT enabled
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.
Domain expiry

176 days

January 6, 2027

SSL certificate

32 days

Issued by Google Trust Services

Domain age

10 years, 5 months

Registered January 6, 2016

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6812:116

Registrar

Cloudflare, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc.
Created January 6, 2016 (10 years, 5 months ago)
Expires January 6, 2027 (8 months)
Last Updated December 7, 2025
Name Servers alexia.ns.cloudflare.com, weston.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700::6812:116
Data source: rdap (0.1s)

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

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.

Why this matters

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

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

Connection waterfall

DNS Lookup 31 ms TCP Connect 17 ms TLS Handshake 20 ms Server Processing 34 ms Content Transfer 0 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9ed523f51b177017-CDG
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: 9ed523f51b177017-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback