Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
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.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
#
#
# _____
# | |
# | | | |
# |_____|
# ____ ___|_|___ ____
# ()___) ()___)
# // /| |\ \\
# // / | | \ \\
# (___) |___________| (___)
# (___) (_______) (___)
# (___) (___) (___)
# (___) |_| (___)
# (___) ___/___\___ | |
# | | | | | |
# | | |___________| /___\
# /___\ ||| ||| // \\
# // \\ ||| ||| \\ //
# \\ // ||| ||| \\ //
# \\ // ()__) (__()
# /// \\\
# /// \\\
# _///___ ___\\\_
# |_______| |_______|
#
#
#
User-agent: *
Disallow: /browse/
Disallow: /enterprise/orgs-terms
Disallow: /package/*/v/*
Disallow: /package/*/*/v/*
User-agent: Googlebot
Allow: /browse/
User-agent: Slurp
Allow: /browse/
User-Agent: msnbot
Allow: /browse/
BTLS Certificate Expiry & Recommendations55 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
BCDN & DeliveryCloudflareREVIEW
A+DNS Records2 A records, 5 ms lookupPASS
| A | 104.17.134.117, 104.17.135.117 |
| AAAA | 2606:4700::6811:8775, 2606:4700::6811:8675 |
| CNAME | — |
| NS | bayan.ns.cloudflare.com, sandy.ns.cloudflare.com |
| MX | 10 aspmx.l.google.com 20 alt1.aspmx.l.google.com 30 alt2.aspmx.l.google.com 40 aspmx2.googlemail.com 50 aspmx3.googlemail.com |
| TXT | 9ppvqgfs31mbchvn33n601dh9sm545j0 MS=ms83736980 ZAMDPQHDY ZOOM_verify_9jQN-O8pSrO7mY5zFjoF6g google-site-verification=3olb25e_eHjiKH_mpKzq8anNryKG7fB3C2Hbrrnny6I google-site-verification=KtNKHWHGMRbAhkVydBWxt9sJJF-vvtTMVK5S8AgtreA status-page-domain-verification=gx37pw1xshfg SPF v=spf1 include:stspg-customer.com include:mail.zendesk.com include:_spf.google.c... |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 81 ms totalPASS
https://npmjs.com
33 ms · HTTP/1.1
https://www.npmjs.com/
49 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://npmjs.com | 301 | 33 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.npmjs.com/ | 200 | 49 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (2 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencenpmjs.com — via MarkMonitor Inc., 16 years, 3 months oldPASS
1676 days
March 19, 2031
55 days
Issued by Google Trust Services
16 years, 3 months
Registered March 19, 2010
Not enabled
Protects against DNS spoofing
Unknown
2606:4700::6811:8775
MarkMonitor Inc.
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