Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 1013 ms totalFIX
https://nysed.gov
298 ms · HTTP/1.1
http://www.nysed.gov/
322 ms · HTTP/1.1
https://www.nysed.gov/
393 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://nysed.gov | 301 | 298 ms | HTTP/1.1 | nginx |
| 2 | http://www.nysed.gov/ | 301 | 322 ms | HTTP/1.1 | nginx |
| 3 | https://www.nysed.gov/ | 200 | 393 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
Redirect directly from https://nysed.gov to https://www.nysed.gov/
Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.
Source: web.dev
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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BHTTP Probe TimingTotal 1423 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations219 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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 Records1 A records, 152 ms lookupPASS
| A | 52.7.171.100 |
| AAAA | — |
| CNAME | — |
| NS | srv21.nysed.gov, dbru.br.ns.els-gms.att.net, dmtu.mt.ns.els-gms.att.net |
| MX | 0 nysed-gov.mail.protection.outlook.com |
| TXT | docker-verification=a52080c7-9c54-4a26-9f34-4dee4129f92e msfpkey=2obadx0ow5f7egp7t9zi3xh8w cisco-ci-domain-verification=ccf4db250380d8452fab51979cb802434aa5fdd30b2aa0c4c1f... MS=ms92383676 cisco-ci-domain-verification=71b16614c92126cab1bc28a6aac177249a034bbb4f280c1e3c3... SPF v=spf1 include:spf.protection.outlook.com ip4:149.10.0.0/16 ip4:184.73.253.171/3... atlassian-domain-verification=tPTJL8eGS0t8L87QfzfAoBd22lQhf36b9Q1U9/kPIF70ORSriL... _globalsign-domain-verification=YIPcHe6fb_y3CSP10ev7oFNyYtywnLteBszIYgazoh |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Crawlabilityrobots.txt present, sitemap with 2 URLsPASS
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used: http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html
# Block crawling of faceted search results to prevent infinite loops
Disallow: /*?f[*
Disallow: /*&f[*
Disallow: /*?search*
Disallow: /search?
# Block AI training scrapers (The "Content Vacuums")
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: CCBot
User-agent: Google-Extended
User-agent: anthropic-ai
User-agent: Bytespider
Disallow: /
# Allow AI Search bots to maintain referral traffic (Optional)
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
Allow: /
# Specific protection for the funding opportunities directory
User-agent: *
Disallow: /funding-opportunities/grants?*
Disallow: /funding-opportunities/grants/*?
Disallow: /standards-instruction/standards-resources-and-supports?*
Disallow: /standards-instruction/standards-resources-and-supports*/?
Disallow: /aepp/welcome-adult-education-programs-and-policy-aepp?*
Disallow: /aepp/welcome-adult-education-programs-and-policy-aepp*/?
User-agent: alexa # Amazon's user agent
Disallow: / # disallow everything
User-agent: Alexabot # Amazon's user agent
Disallow: / # disallow everything
User-agent: AlexaToolbar # Amazon's user agent
Disallow: / # disallow everything
User-agent: Aranhabot # Amazon's user agent
Disallow: / # disallow everything
User-agent: amazon-QBusiness # Amazon Q Web Crawler
Disallow: / # disallow everything
User-agent: Amazon CloudFront # Amazon's user agent
Disallow: / # disallow everything
User-agent: Amazonbot # Amazon's user agent
Disallow: / # disallow everything
User-agent: amzn_assoc # Amazon's user agent
Disallow: / # disallow everything
User-agent: amazon-kendra-web-crawler-* # all customers of Amazon Kendra's web crawler
Disallow: / # disallow everything
User-agent: amazon-kendra # all customers of Amazon Kendra's web crawler
Disallow: / # disallow everything
User-agent: AmazonAdBot # Amazon's user agent
Disallow: / # disallow everything
User-agent: AmazonProductDiscoverybot # Amazon's user agent
Disallow: / # disallow everything
User-agent: AWS* # Amazon's user agent
Disallow: / # disallow everything
User-agent: aws-internal # Amazon's user agent
Disallow: / # disallow everything
User-agent: aws* # Amazon's user agent
Disallow: / # disallow everything
User-agent: echo # Amazon's user agent
Disallow: / # disallow everything
User-agent: echo* # Amazon's user agent
Disallow: / # disallow everything
User-agent: *Glue # Amazon's user agent
Disallow: / # disallow everything
User-agent: Storebot-Google # Google's user agent
Disallow: / # disallow everything
User-agent: Googlebot-Image # Google's user agent
Disallow: / # disallow everything
User-agent: Googlebot-News # Google's user agent
Disallow: / # disallow everything
User-agent: Googlebot-News # Google's user agent
Disallow: / # disallow everything
User-agent: Googlebot-Video # Google's user agent
Disallow: / # disallow everything
User-agent: AdsBot-Google-Mobile # Google's user agent
Disallow: / # disallow everything
User-agent: Mediapartners-Google # Google's user agent
Disallow: / # disallow everything
User-agent: FeedFetcher-Google # Google's user agent
Disallow: / # disallow everything
User-agent: GoogleProducer # Google's user agent
Disallow: / # disallow everything
User-agent: GoogleOther # Google's user agent
Disallow: / # disallow everything
User-agent: Google-Extended # Google's user agent
Disallow: / # disallow everything
User-agent: APIs-Google # Google's user agent
Disallow: / # disallow everything
User-agent: *
Crawl-delay: 10
# Directories
Disallow: /includes/
Disallow: /misc/
Disallow: /modules/
Disallow: /profiles/
Disallow: /scripts/
Disallow: /themes/
Disallow: /COMS/
Disallow: /stateaid/
Disallow: /cafe/
Disallow: /heds/
Disallow: /dpls/
Disallow: /tapeusage/
Disallow: /cn/
Disallow: /fm/
Disallow: /fmis/
Disallow: /stateaid/
# Files
Disallow: /CHANGELOG.txt
Disallow: /cron.php
Disallow: /INSTALL.mysql.txt
Disallow: /INSTALL.pgsql.txt
Disallow: /INSTALL.sqlite.txt
Disallow: /install.php
Disallow: /INSTALL.txt
Disallow: /LICENSE.txt
Disallow: /MAINTAINERS.txt
Disallow: /update.php
Disallow: /UPGRADE.txt
Disallow: /xmlrpc.php
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips/
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register/
Disallow: /user/password/
Disallow: /user/login/
Disallow: /user/logout/
Disallow: /seduser
# Paths (no clean URLs)
Disallow: /?q=admin/
Disallow: /?q=comment/reply/
Disallow: /?q=filter/tips/
Disallow: /?q=node/add/
Disallow: /?q=search/
Disallow: /?q=user/password/
Disallow: /?q=user/register/
Disallow: /?q=user/login/
Disallow: /?q=user/logout/
Disallow: /homepage-slider/*
Disallow: /node/4695
Sitemap: http://www.nysed.gov/sitemap.xml
A+Domain Intelligencenysed.gov — via get.gov, 28 years, 11 months old, hosted on AWSPASS
143 days
November 3, 2026
219 days
Issued by GlobalSign nv-sa
28 years, 11 months
Registered October 2, 1997
Not enabled
Protects against DNS spoofing
AWS
ASN AS14618
52.7.171.100
get.gov
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