nd.gov Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of nd.gov on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 55056ms. The page is served over HTTP/2 protocol, however no compression (Gzip or Brotli) is enabled, which means the page is transferred at its full uncompressed size. The total page weight is 95 KB.
Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted.
The security headers analysis reveals a score of 50/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, and X-Content-Type-Options. However, the site is missing Content-Security-Policy, Referrer-Policy, and Permissions-Policy, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks.
Our technology detection scan identified 7 technologies across 7 categories powering nd.gov. The detected stack includes Drupal, Bootstrap 5.3.8, Vite, Google Analytics 4, VWO, jQuery, and Font Awesome.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, nd.gov receives an overall trust score of 70/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time55056ms
ProtocolHTTP/2
Page Size95 KB
CompressionNone
Compression SavingsN/A
CDNNo
ServerState of North Dakota
Total Requests247
3rd Party Domains11
Redirect1 hop(s)
Detected Technologies (7)
• Drupal
🎨 Bootstrap
🔨 Vite
📊 Google Analytics 4
🧪 VWO
📦 jQuery
🎯 Font Awesome
Security Headers
✗
Content-Security-Policy
Not set
✓
Strict-Transport-Security (HSTS)
Set ✓
✓
X-Content-Type-Options
Set ✓
✗
Referrer-Policy
Not set
✗
Permissions-Policy
Not set
SSL Certificate
IssuerSectigo Limited
Issuer FullcountryName=GB, organizationName=Sectigo Limited, commonName=Sectigo Public Server Authentication CA OV E36
SubjectcountryName=US, stateOrProvinceName=North Dakota, organizationName=State of North Dakota, commonName=www.nd.gov
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
nd.gov Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, nd.gov receives a trust score of 70/100, which places it in the "Likely Safe" category. This score is calculated by evaluating multiple factors including SSL certificate validity, domain registration history, email authentication protocols, security header configuration, and blacklist status across major threat intelligence databases.
The analysis identified several positive trust signals: a valid HTTPS connection protecting data in transit, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification.
Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, missing Referrer-Policy, potentially leaking URL information to third parties, the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity, and DNSSEC is not enabled, leaving DNS queries vulnerable to spoofing attacks. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved.
We checked nd.gov against 8 major blacklist databases including Google Safe Browsing, Phishtank, Urlhaus, Openphish, Dnsfilter, Spamhaus Dbl, Surbl, and Virustotal. The domain passed all 8 checks with a clean status, meaning it has not been flagged for phishing, malware distribution, spam, or other malicious activities by any of the tested threat intelligence providers.
Trust Signals
✅ Valid HTTPS
✅ HSTS enabled
✅ SPF configured
✅ DMARC configured (p=none)
✅ DKIM configured
⚠️ DNSSEC not enabled
✅ Sitemap.xml found
⚠️ Missing Content-Security-Policy
⚠️ Missing Referrer-Policy
Blacklist Checks (8/8 clean)
✓
Google Safe Browsing
clean
✓
Phishtank
clean
✓
Urlhaus
clean
✓
Openphish
clean
✓
Dnsfilter
clean
✓
Spamhaus Dbl
clean
✓
Surbl
clean
✓
Virustotal
clean
nd.gov Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned nd.gov and identified 7 distinct technologies across 7 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records.
CMS: Drupal — manages the content and page structure for nd.gov.
CSS Framework: Bootstrap (version 5.3.8) — provides the styling and responsive layout system for nd.gov.
Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for nd.gov.
Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for nd.gov.
A/B Testing: VWO — enables experimentation and conversion optimization for nd.gov.
JavaScript Library: jQuery — provides utility functions and DOM manipulation for nd.gov.
Icon Set: Font Awesome — provides additional functionality for nd.gov.
We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-E6CRFY4N12. These IDs can be used to identify other websites operated by the same organization.
CMS
CSS Framework
Build Tool
Analytics
📊 Google Analytics 4(95%)
A/B Testing
JavaScript Library
Icon Set
Tracking IDs
nd.gov Performance, Speed & Core Web Vitals
🤖 AI Summary
nd.gov delivers its homepage in 55056ms (server response time), which is considered slow by industry standards. The total page weight is 95 KB, and we detected 247 resource requests loading assets from 11 third-party domains. A high number of third-party domains can significantly impact page load time due to additional DNS lookups and TLS handshakes required for each domain.
No compression is currently enabled on nd.gov. Enabling Brotli or Gzip compression could reduce page size by 60-80% for text-based assets (HTML, CSS, JavaScript), significantly improving load times and reducing bandwidth costs. This is one of the simplest and most impactful performance optimizations available.
Asset minification status: 0 out of 4 CSS files and 7 out of 68 JavaScript files are minified. Minifying the remaining 65 unminified file(s) could further reduce page weight by 10-30% for those assets. Minification is a best practice that reduces download sizes without affecting functionality.
From an environmental perspective, each page view of nd.gov produces approximately 0.05g of CO₂, earning a carbon rating of A. This places the website among the cleanest on the web, demonstrating efficient use of server resources and optimized content delivery. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 95 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for nd.gov. This typically means the site doesn't have enough real-world Chrome user traffic to generate statistically significant field data, or the domain is not included in the CrUX dataset. Core Web Vitals (LCP, INP, CLS) are important Google ranking factors that measure real user experience.
Core Web Vitals data not available
Requires CrUX API key configuration
Carbon Footprint
CO₂ per page view0.05g
RatingA
Page Weight & Optimization
HTML Size95 KB
CompressionNone
Compression SavingsN/A
CDNNo
Total Requests247
3rd Party Domains11
CSS Minified0/4
JS Minified7/68
nd.gov DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
nd.gov resolves to the IPv4 address 165.234.159.38, but does not support IPv6. IPv6 adoption is increasingly important as IPv4 address space becomes exhausted, and some ISPs and regions are transitioning to IPv6-only connectivity. The domain has 1 A record(s) configured.
The domain name system is managed by 2 name servers: ns1.ndnic.net and ns2.ndnic.net. Having 2 name servers provides good redundancy — if one fails, the others can continue serving DNS queries. The choice of name servers often indicates the DNS hosting provider or CDN service being used.
Email for nd.gov is handled by Microsoft 365 with 1 MX records configured: nd-gov.mail.protection.outlook.com. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server.
SPF (Sender Policy Framework) is configured, which specifies which mail servers are authorized to send email on behalf of this domain. This helps prevent email spoofing and improves email deliverability. DMARC (Domain-based Message Authentication, Reporting and Conformance) is configured with a none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. DKIM (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit.
DNSSEC is not enabled for nd.gov. While not critical for most websites, DNSSEC adds an important security layer by ensuring DNS responses haven't been tampered with during transit. Enabling DNSSEC is recommended for domains handling sensitive data or financial transactions.
Our subdomain enumeration scan discovered 4 active subdomains for nd.gov: apps.nd.gov, support.nd.gov, webmail.nd.gov, and www.nd.gov. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
NS
ns1.ndnic.net
ns2.ndnic.net
MX
nd-gov.mail.protection.outlook.com
Email & Authentication
MX ProviderMicrosoft 365
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (4 found)
apps.nd.gov support.nd.gov webmail.nd.gov www.nd.gov
nd.gov Page Content, Images & Accessibility
🤖 AI Summary
The homepage of nd.gov contains 739 words of visible text content. This is a moderate amount of content. The page is structured with 5 H2 headings, 0 H3 headings, 0 H4 headings.
The page includes 12 images. 2 images (17%) are missing alt text attributes, which is a significant concern for both accessibility and SEO. Screen readers rely on alt text to describe images to visually impaired users, and search engines use alt text to understand image content. Only 83% of images have proper alt text — we recommend adding descriptive alt attributes to all images.
The link structure consists of 132 internal links pointing to other pages on the same domain and 27 external links pointing to third-party websites. The high number of internal links suggests a well-interconnected site structure, which helps search engines discover and crawl all pages efficiently. There are 68 external JavaScript files, 4 CSS stylesheets, and 0 iframes on the page.
The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages).
Notable missing features: robots.txt and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.
We detected the following payment methods accepted on nd.gov: Discover. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.
Content Structure
H1North Dakota State Government - ND Portal
H2 Tags5
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links132
External Links27
Assets & Features
JavaScript Files68
JS Minified7/68
CSS Files4
CSS Minified0/4
Iframes0
Images12
Missing Alt2
SitemapYes ✓
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
Payment Methods Detected
nd.gov SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for nd.gov is well-optimized at 48 characters: "Home | North Dakota State Government - ND Portal". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation.
No meta description is configured for nd.gov. This is a critical SEO oversight — without a meta description, Google will auto-generate a snippet from page content, which may not accurately represent the page or entice users to click. Adding a unique, compelling meta description of 120-155 characters is strongly recommended.
The canonical url is correctly set to https://www.nd.gov/home, preventing duplicate content issues, the page language is declared as en, the meta robots directive is set to max-image-preview:standard, and a favicon is configured.
Open Graph meta tags are configured with 2/4 recommended fields: OG title ("Home..."), OG image (social sharing thumbnail), These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol.
A Twitter Card of type summary_large_image is configured, which controls how links appear when shared on Twitter/X. The "summary_large_image" type displays a large image preview, which typically generates higher engagement rates than the basic card type.
Google SERP Preview
Home | North Dakota State Government - ND Portal
https://nd.gov
Meta Tags
TitleHome | North Dakota State Government - ND Portal...
Title Length48 chars
Meta Desc Length0 chars
H1North Dakota State Government - ND Portal
Languageen
Canonicalhttps://www.nd.gov/home
Meta Robotsmax-image-preview:standard
Meta Keywordsnot set
Schema.org & Social
Schema Types—
OG Type—
OG ImageSet ✓
Twitter Cardsummary_large_image
FaviconSet ✓
Open Graph Preview
nd.gov Related Domains & Cross-References
🤖 AI Summary
Related domain discovery works by finding other websites that share the same IP address, Google Tag Manager container ID, Google Analytics property, or advertising pixel IDs with nd.gov. This data becomes available after batch-crawling the domain database — individual domain lookups cannot populate this section. We extracted the following tracking IDs that can be used for cross-referencing: ga4_id: G-E6CRFY4N12.
Tracking IDs for Cross-Referencing
Related Domains
Related domain data requires database (populated after batch crawl)