Skip to content
https://nc.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

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
A
DNS Records
1 A records, 335 ms lookup
PASS
1 A records, 335 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 52.204.9.77
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: ns1.nc.gov, ns2.nc.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 (335 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 335 ms
A52.204.9.77
AAAA
CNAME
NSns1.nc.gov, ns2.nc.gov
MX
0 nc-gov.mail.protection.outlook.com
TXT
google-site-verification=o1IVDquF1h8MkBGhsNykAf7nLMjSZ_BillgY2GZs13E
docusign=ed50f81d-5529-4c68-96d6-b0528b6d3acf
z1X0HwkAwPrOPP4571tVJUK7TXSYPrXhENFcp/NBb/ahpKUeW653YLitlTT3ZuMthJFFBIhJom7Glg0D...
bcp6WczRPE5xTS55UI0f8QOJI0SbR2ofLuW1ppbgOqS4UDF4xpNuCTFpnyYdjuSuzsK5kB3gVdQNQfaK...
docusign=a27fc5af-cef6-4734-95e1-4b825783c547
iContact1787918
tR9ljkxvUDVAk4EYc/AUHork2R+k4Qs0CgyeA+j8qSXCAtPfafER5mLQ7GfjZAtUinEu02olQ8wKdsv7...
218c5173-5d5f-4ff9-9e7c-6ee4ef3288a2
00Dcs00000ARqkj=1TBcs0000000FDZ
apple-domain-verification=Kr3aavXko8G3A5SF
87f1e6e9-f46f-4e99-abe6-b82ebf7b466d
dpkfp8cy166vrk0hzjfglq1c10gxfgw1
00DSK000004z1Cz=1TBSK000000001d
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
MS=ms98626480
asv=2d47a2a3d2771dd5b278617f830ed579
cisco-ci-domain-verification=690c6479303bd001463931ac975e62c21b6e6642b07fecc4cd4...
adobe-idp-site-verification=6f16ebfc0f5e16ebdb897e81bac152353cde8e97aa65a61f3793...
-asv=1ba1a9675602c5a694f975143b5fe756
CAALookup not available with standard resolver
Resolved in 335 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), 603 ms total
PASS
1 redirect(s), 603 ms total
Info::
Single redirect
Got: https://nc.gov → https://www.nc.gov/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 603 ms total
Got: 603 ms

https://nc.gov

299 ms · HTTP/1.1

301

https://www.nc.gov/

304 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nc.gov301299 msHTTP/1.1Apache
2https://www.nc.gov/200304 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 80 URLs
PASS
robots.txt present, sitemap with 80 URLs
Info::
robots.txt is present
Got: 1790 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 80 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1790 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
#

# 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


User-agent: *

# CSS, JS, Images

Allow: /core/*.css$

Allow: /core/*.css?

Allow: /core/*.js$

Allow: /core/*.js?

Allow: /core/*.gif

Allow: /core/*.jpg

Allow: /core/*.jpeg

Allow: /core/*.png

Allow: /core/*.svg

Allow: /profiles/*.css$

Allow: /profiles/*.css?

Allow: /profiles/*.js$

Allow: /profiles/*.js?

Allow: /profiles/*.gif

Allow: /profiles/*.jpg

Allow: /profiles/*.jpeg

Allow: /profiles/*.png

Allow: /profiles/*.svg

# Directories

Disallow: /core/

Disallow: /profiles/

# Files

Disallow: /README.txt

Disallow: /web.config

# 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/

# Paths (no clean URLs)

Disallow: /index.php/admin/

Disallow: /index.php/comment/reply/

Disallow: /index.php/filter/tips

Disallow: /index.php/node/add/

Disallow: /index.php/search/

Disallow: /index.php/user/password/

Disallow: /index.php/user/register/

Disallow: /index.php/user/login/

Disallow: /index.php/user/logout/

# DS Additions

Disallow: /user

Disallow: /user/login

Sitemap: https://www.nc.gov/sitemap.xml
Sitemap: https://www.nc.gov/sitemap.xml
A+
Domain Intelligence
nc.gov — via get.gov, 24 years, 1 months old, hosted on AWS
PASS
nc.gov — via get.gov, 24 years, 1 months old, hosted on AWS
Info::
Domain registered until Aug 20, 2026 (3 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

66 days

August 20, 2026

SSL certificate

37 days

Issued by Let's Encrypt

Domain age

24 years, 1 months

Registered July 22, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

52.204.9.77

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 July 22, 2002 (24 years, 1 months ago)
Expires August 20, 2026 (3 months)
Last Updated August 25, 2025
Name Servers ns1.nc.gov, ns2.nc.gov
DNSSEC Not enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 52.204.9.77
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.6s)

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

Connection waterfall

DNS Lookup 127 ms TCP Connect 98 ms TLS Handshake 101 ms Server Processing 102 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback