Skip to content
https://nj.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
5
PASS
4
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
4 PASS 5 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
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 351 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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 351 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /Support/agriculture/
Allow: /Support/agriculture
Allow: /Support/nj/
Allow: /Support/nj
Disallow: /cgi-bin/homelandsecurity/
Disallow: /cgi-bin/dobi/licenseesearch/
Disallow: /cgi-bin/consumeraffairs/search/
Disallow: /cgi-bin/state/
Disallow: /Support/
Disallow: /treasury/treasdocuments/
Disallow: /highereducation/higheddocs/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.nj.gov/
200https://nj.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://nj.gov/ → https://nj.gov/

Consistent

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Incapsula
REVIEW
Incapsula
Info::
Site is served via Incapsula CDN
Got: x-iinfo: 5-12156381-12156383 NNYY CT(27 26 0) RT(1776805561114 20) q(0 0 0 0) r(0 0) U12
CDN Detected: Incapsula
Provider Incapsula Evidence x-iinfo: 5-12156381-12156383 NNYY CT(27 26 0) RT(1776805561114 20) q(0 0 0 0) r(0 0) U12
A+
DNS Records
2 A records, 6 ms lookup
PASS
2 A records, 6 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 45.60.135.108, 45.60.75.108
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1.nj.gov, ns2.nj.gov, ns3.nj.gov, ns4.nj.gov
Info::
2 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: 6 ms
Got: 6 ms
A45.60.135.108, 45.60.75.108
AAAA—
CNAME—
NSns1.nj.gov, ns2.nj.gov, ns3.nj.gov, ns4.nj.gov
MX
10 mxb-0000da01.gslb.pphosted.com
10 mxa-0000da01.gslb.pphosted.com
TXT
MS=ms59609015
_ozq1g4dxuwsziqh9c68he4zk6v57f04
apple-domain-verification=jiD9uROOeBsLSV3V
openai-domain-verification=dv-fG36hghlHwaJCokUwjeXPGbz
google-site-verification=HarM6cYGTpT4mTdJuKt1LucvJyhee3Z00U3BIErVufc
google-site-verification=TgD7U574OM9hqqN7iP3k9S5lUGFRVdETOW6bACbA6fY
T8raq2B77hi+5013d+0D7TY6DgrV3sQZLm8IG70q+E10DEv59+Ms58G1VoLSaxvNCDr1Yo4rxBUEb4p4...
adobe-idp-site-verification=b677311e5f526cfed15100a771d25525b80a78f5bd6e85b1b1e8...
SPF v=spf1 include:spf-sonj.nj.gov include:spf-0000da01.pphosted.com ip4:20.42.36.97...
CAALookup not available with standard resolver
Resolved in 6 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://nj.gov

https://nj.gov

57 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nj.gov20057 msHTTP/1.1
A+
Domain Intelligence
nj.gov — via get.gov, 25 years old, hosted on INCAPSULA - Incapsula Inc, US
PASS
nj.gov — via get.gov, 25 years old, hosted on INCAPSULA - Incapsula Inc, US
Info::
Domain registered until Aug 12, 2026 (3 months remaining)
Info::
DNSSEC is enabled
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: INCAPSULA - Incapsula Inc, US
Got: AS19551
Domain expiry

26 days

August 12, 2026

SSL certificate

73 days

Issued by GlobalSign nv-sa

Domain age

25 years

Registered August 28, 2001

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

INCAPSULA - Incapsula Inc, US

ASN AS19551

45.60.75.108

Registrar

get.gov

Unlocked 4 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 registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar get.gov
Created August 28, 2001 (25 years ago)
Expires August 12, 2026 (3 months)
Last Updated August 17, 2025
Name Servers ns1.nj.gov, ns2.nj.gov, ns3.nj.gov, ns4.nj.gov
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 45.60.75.108
ASN AS19551 (INCAPSULA - Incapsula Inc, US)
Provider INCAPSULA - Incapsula Inc, US
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 5 ms TCP Connect 16 ms TLS Handshake 19 ms Server Processing 62 ms Content Transfer 50 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback