Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
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
<html>
<head>
<META NAME="robots" CONTENT="noindex,nofollow">
<script src="/_Incapsula_Resource?SWJIYLWA=5074a744e2e3d891814e9a2dace20bd4,719d34d31c8e3a6e6fffd425f7e032f3">
</script>
<body>
</body></html>
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations243 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
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
A+DNS Records2 A records, 25 ms lookupPASS
| A | 199.83.128.97, 199.83.129.97 |
| AAAA | — |
| CNAME | — |
| NS | ns-1399.awsdns-46.org, ns-1737.awsdns-25.co.uk, ns-263.awsdns-32.com, ns-630.awsdns-14.net |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | 4d36bc720531f36a2e6ac75c2d5d3604ace6f29f267615989ff96bdd4475e6d9392c9b8429992f71... 8d73qf58ci1pfio25hvlqhm3ha MS=40EC1ECE06B86D5A78E34623F5BE99F62F94A48C _globalsign-domain-verification=ByJ2YaFY9XbAYqsah-2MtGzB11PBqfDI58fIMhh5VV anthropic-domain-verification-v99hg6=f0nMF66WXlC9z3UWVHe7LzHCX apple-domain-verification=2IBGSCICxy5yKngo atlassian-domain-verification=iYCB5pwb98729L6ocVl5eVZb3F5/yXei3xvIDzQ33RJlOVGxlv... canva-site-verification=fN6pRArETkJzJOWLZGWFiQ globalsign-domain-verification=12c79aac93c6090746e8e65e38ee08fa globalsign-domain-verification=18a821a5b8d29e311621ed4193292d10 globalsign-domain-verification=19C17979AA4B4235E1BEC3BAD7E4D672 globalsign-domain-verification=22918B9E13976891E4EA7BCF3294F592 globalsign-domain-verification=74AB9EA9A442C17FD4E7E6482BADB7FA globalsign-domain-verification=D0564ADC5BB1FA20C089D3FAE7D81EC9 globalsign-domain-verification=E12487B9905503C811BE1013071ED570 globalsign-domain-verification=F3BC5AC4D30333773BB8D854864F6D6B google-site-verification=Ez0rQUSaSMlOrZRgtzFKAjSbTwP-8uHG37eLdvgW9pw google-site-verification=VRgAU0zcV1289fi_NjfkdYx91uoJZWIj-Vn8viNetOs google-site-verification=XCvYTBX2Xjn-MBL7DtkQWpJtb8PDYuGEUANCdt0PZLM google-site-verification=_shbOK1otHA_eFNFgJsOwITZrWQwRg4wr8nmrJPNVDM google-site-verification=a-v2IIfK4MWr70Io4ioL2tMNGtCmK-xCWgSLwBiTCVc google-site-verification=hAGDySTrvQCeu8nD3qrhHf93sexH6H_gsiKIAwMVcNQ google-site-verification=wdOkiwl-_MYXnLNSh1fIkLPueblMqNGsElqnejASI8w google-site-verification=yElS163xqUuMxti1ltzLf7MxkDU9dIGMMxpQmxGsPCk google-site-verification=z9e04K0FyFKF5NK6qdYxZAJHyLAQMl-G0x1BQ8xQJbw jamf-site-verification=47nV34Il-f0gnmymwLe_wQ miro-verification=341282f0a187ba3683a2d7ec74ec536ccab10e36 SPF v=spf1 include:_spf.google.com include:_s00710534.autospf.email ~all |
| 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), 77 ms totalPASS
https://nypl.org
55 ms · HTTP/1.1
https://www.nypl.org/
22 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://nypl.org | 301 | 55 ms | HTTP/1.1 | |
| 2 | https://www.nypl.org/ | 200 | 22 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligencenypl.org — via CSC Corporate Domains, Inc., 35 years, 7 months old, hosted on INCAPSULA - Incapsula Inc, USPASS
258 days
February 27, 2027
243 days
Issued by Corporation Service Company
35 years, 7 months
Registered February 26, 1991
Not enabled
Protects against DNS spoofing
INCAPSULA - Incapsula Inc, US
ASN AS19551
199.83.128.97
CSC Corporate Domains, 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