Skip to content
https://ny.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
1 A records, 1543 ms lookup
PASS
1 A records, 1543 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 107.20.176.212
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns2.ny.gov, ns3.ny.gov
Info::
1 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
Warning::
DNS resolution is slow (1543 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 1543 ms
A107.20.176.212
AAAA
CNAME
NSns2.ny.gov, ns3.ny.gov
MX
10 ny-gov.mail.protection.outlook.com
TXT
MS=ms20020510
webexdomainverification.88BZP=806f36e2-f5ea-450a-a375-9761bce71aea
_globalsign-domain-verification=UETYJRFDNhMYPpRF9UM-uv2E92Udm9goeiFE1HGu3y
facebook-domain-verification=gki8c2w5pfo1beu1z3ndv9poc23q16
webexdomainverification.EMWY=8ab46346-b600-4cf1-b8b0-3e2476f1f99f
wombat-verification=3KwxVCQV1HEp-aRXRTKKaZ5G0frhk
SPF v=spf1 mx ip4:170.123.0.0/16 ip4:161.11.224.0/22 include:svc.ny.gov include:serv...
MS=ms59102469
HXEKhSjzzZC4mnYfhoTpErlwm1yVqpTSyUgYIRglDDy7M4zUFN3UjXJ+p1ma6IIuFhoNVkxLLAYxw5U0...
MV2-MJ6-BR9
google-site-verification=XCye-D6cc9kydrkmaqnNIjlMYQuupkb-i_qztp_Eslc
google-site-verification=xF9LEy9qzVytU3p0HfWhFA_LdO0o7SfJt8ecyGVpM1k
ZOOM_verify_wB_AZlgnSVm7yQyEJSIpng
webexdomainverification.JNDC=b730112b-28e8-4cbb-9491-74b8603deecb
_globalsign-domain-verification=SzWAMYeEnKGvq8VvGcWdNYAXzeKtle0lujFTWqUaI_
_globalsign-domain-verification=MJ4uwagM31e8xr2YhyjfrAGVRFl6aBuGrnkluWZzuU
globalsign-domain-verification=FFA7F053BA862C377AD75C80BBFB78BF
_globalsign-domain-verification=7Lc5qtpA-RpuzBxR3qoJoeGlRK5funy-0kFltbo8Ps
webexdomainverification.7MXNM=077354b7-e7e5-4b43-966a-08ffc70b3f79
webexdomainverification.=9dca8b5b-5723-4291-a80f-17e41ebc4311
CAALookup not available with standard resolver
Resolved in 1543 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A
Redirect Chain
1 redirect(s), 475 ms total
PASS
1 redirect(s), 475 ms total
Info::
Single redirect
Got: https://ny.gov → https://www.ny.gov/ (301)
Info::
WWW normalization redirect

https://ny.gov

289 ms · HTTP/1.1

301

https://www.ny.gov/

186 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ny.gov301289 msHTTP/1.1nginx
2https://www.ny.gov/403186 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.ny.gov/
200https://ny.gov/

HTTP → HTTPS

301http://ny.gov/ https://www.ny.gov/

Consistent

A+
Domain Intelligence
ny.gov — via get.gov, 23 years, 11 months old, hosted on AWS
PASS
ny.gov — via get.gov, 23 years, 11 months old, hosted on AWS
Info::
Domain registered until Sep 30, 2026 (5 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: get.gov
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.
Info::
Hosting: AWS
Got: AS14618
Domain expiry

78 days

September 30, 2026

SSL certificate

90 days

Issued by GlobalSign nv-sa

Domain age

23 years, 11 months

Registered September 18, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

107.20.176.212

Registrar

get.gov

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar get.gov
Created September 18, 2002 (23 years, 11 months ago)
Expires September 30, 2026 (5 months)
Last Updated October 5, 2025
Name Servers ns1.ny.gov, ns2.ny.gov
DNSSEC Not enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 107.20.176.212
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.5s)

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 420 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
131 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
95 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
98 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
420 ms
Total Time Total request time from DNS lookup through full response.
420 ms

Connection waterfall

DNS Lookup 131 ms TCP Connect 95 ms TLS Handshake 98 ms Server Processing 96 ms Content Transfer 0 ms
A+
CDN & Delivery
Varnish (HIT)
PASS
Varnish (HIT)
Info::
Site is served via Varnish CDN
Got: via: varnish
Info::
CDN cache status: HIT
CDN Detected: Varnish
Provider Varnish Cache Status HIT Evidence via: varnish
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback