Skip to content
https://cbp.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
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.cbp.gov/
200https://cbp.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
1 A records, 13 ms lookup
PASS
1 A records, 13 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 173.222.156.2
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:1419:6a00:a82::447a, 2600:1419:6a00:a87::447a
Info::
6 nameserver(s) configured
Got: a1-91.akam.net, a7-64.akam.net, a8-65.akam.net, a9-66.akam.net, a16-67.akam.net, a22-66.akam.net
Info::
No MX records — email not configured via DNS
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: 13 ms
Got: 13 ms
A173.222.156.2
AAAA2600:1419:6a00:a82::447a, 2600:1419:6a00:a87::447a
CNAME—
NSa1-91.akam.net, a7-64.akam.net, a8-65.akam.net, a9-66.akam.net, a16-67.akam.net, a22-66.akam.net
MX—
TXT
SPF v=spf1 -all
00dt00000004xm5eam
00dt0000000klzkeam
00dt0000000lbimea4
00dt0000000lbusea4
00dt0000000pn1zeaw
00dt0000000pndmea4
00dt0000000tzc7eao
00dt0000000tziaea4
amazonses:jY3wjqyz2x8L04lodqSQqhQfcfXZ0G3+31ugtSgwSn0=
google-site-verification=8a3SUUlFQoMPJy4Xs5qsC5JR60Ja2ZVlSjFtg2J0NLY
v=DMARC1; p=reject; fo=1; rua=mailto:DMARC@hq.dhs.gov, mailto:reports@dmarc.cybe...
CAALookup not available with standard resolver
Resolved in 13 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), 213 ms total
PASS
1 redirect(s), 213 ms total
Info::
Single redirect
Got: https://cbp.gov → https://www.cbp.gov/ (301)
Info::
WWW normalization redirect

https://cbp.gov

36 ms · HTTP/1.1

301

https://www.cbp.gov/

176 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cbp.gov30136 msHTTP/1.1AkamaiGHost
2https://www.cbp.gov/200176 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2600:1419:6a00:a82::447a, 2600:1419:6a00:a87::447a
Got: 2 ms connect
IPv6 Ready
AAAA Records 2600:1419:6a00:a82::447a, 2600:1419:6a00:a87::447a Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 16 URLs
PASS
robots.txt present, sitemap with 16 URLs
Info::
robots.txt is present
Got: 2295 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 16 entries
Info::
Sitemap index with 16 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 2295 B Sitemaps referenced 0 User-agents *, PetalBot 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.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
# 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: /media/oembed
Disallow: /*/media/oembed
# 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

#Disallow the profile directory as per OPA request 2/1/24
Disallow: /profile/
Disallow: /profile/*
#Disallow the files/assets/documents directory 10/04/24
Disallow:  /sites/default/files/assets/documents/
Disallow:  /sites/default/files/assets/documents/*
User-agent: PetalBot
Disallow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 16 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
cbp.gov — via get.gov, 23 years, 4 months old
PASS
cbp.gov — via get.gov, 23 years, 4 months old
Info::
Domain registered until Sep 2, 2026 (4 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.
Domain expiry

48 days

September 2, 2026

SSL certificate

191 days

Issued by DigiCert Inc

Domain age

23 years, 4 months

Registered April 2, 2003

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2600:1419:6a00:a82::447a

Registrar

get.gov

Unlocked 6 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 April 2, 2003 (23 years, 4 months ago)
Expires September 2, 2026 (4 months)
Last Updated September 7, 2025
Name Servers a1-91.akam.net, a16-67.akam.net, a22-66.akam.net, a7-64.akam.net, a8-65.akam.net, a9-66.akam.net
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2600:1419:6a00:a82::447a
Data source: rdap (0.5s)

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 51 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.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
18 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
52 ms
Total Time Total request time from DNS lookup through full response.
52 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 0 ms TLS Handshake 18 ms Server Processing 28 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