Skip to content
https://ojp.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
6 PASS 2 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
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.ojp.gov/
200https://ojp.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://ojp.gov/ → https://ojp.gov/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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, 7 ms lookup
PASS
1 A records, 7 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 149.101.127.150
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2607:f330:5000:3030:101::96
Info::
2 nameserver(s) configured
Got: jonah.ns.cloudflare.com, novalee.ns.cloudflare.com
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: 7 ms
Got: 7 ms
A149.101.127.150
AAAA2607:f330:5000:3030:101::96
CNAME—
NSjonah.ns.cloudflare.com, novalee.ns.cloudflare.com
MX
10 mx-da6.usdoj.gov
10 mx-dc2.usdoj.gov
TXT
v=DMARC1;p=reject;rua=mailto:reports@dmarc.cyber.dhs.gov,mailto:dmarcreports@usd...
SPF v=spf1 include:_spf.usdoj.gov -all
CAALookup not available with standard resolver
Resolved in 7 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.

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

https://ojp.gov

607 ms · HTTP/1.1

301

https://www.ojp.gov/

169 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ojp.gov301607 msHTTP/1.1
2https://www.ojp.gov/200169 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (167 ms)
PASS
IPv6 reachable (167 ms)
Info::
IPv6 is configured and reachable at 2607:f330:5000:3030:101::96
Got: 167 ms connect
IPv6 Ready
AAAA Records 2607:f330:5000:3030:101::96 Connection Reachable (167 ms)
A+
Crawlability
robots.txt present, sitemap with 73 URLs
PASS
robots.txt present, sitemap with 73 URLs
Info::
robots.txt is present
Got: 1974 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 73 entries
Info::
Sitemap index with 73 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1974 B Sitemaps referenced 1 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

Disallow: /node/*

Disallow: /glossary/*

Disallow: /media/oembed

Disallow: /*/media/oembed

Disallow: /topics/program/*

Disallow: /topics/practice/*

# 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

Disallow: /index.php/media/oembed

Disallow: /index.php/*/media/oembed

# OVC NCVRW Award forms

Disallow: /nomination/*
# Simple sitemap
Sitemap: https://ojp.gov/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 73 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
ojp.gov — via get.gov, 27 years, 10 months old
PASS
ojp.gov — via get.gov, 27 years, 10 months old
Info::
Domain registered until Aug 21, 2026 (4 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.
Domain expiry

67 days

August 21, 2026

SSL certificate

115 days

Issued by DigiCert Inc

Domain age

27 years, 10 months

Registered November 12, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2607:f330:5000:3030:101::96

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 November 12, 1998 (27 years, 10 months ago)
Expires August 21, 2026 (4 months)
Last Updated August 26, 2025
Name Servers jonah.ns.cloudflare.com, novalee.ns.cloudflare.com
DNSSEC Not enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2607:f330:5000:3030:101::96
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 610 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
9 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
119 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
360 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
610 ms
Total Time Total request time from DNS lookup through full response.
610 ms

Connection waterfall

DNS Lookup 9 ms TCP Connect 119 ms TLS Handshake 360 ms Server Processing 122 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