Is congress.gov legit?

68
/ 100
Mostly Safe
Industry: Government

While congress.gov benefits from a long-standing domain and robust infrastructure, several basic elements of transparency and legal compliance are surprisingly absent. Key information like contact details and essential legal pages are missing, which is highly unusual for a site of this importance, indicating that while it's likely legitimate, there are areas for improvement in its user-facing presentation.

Government average: 80/100 · based on 33 sites

Checked: April 18, 2026 at 8:00 AM UTC · Refresh

Is congress.gov a scam? Here's what we found.

Security 90/100

The security setup is strong, featuring a valid SSL certificate with modern TLS 1.3 encryption and a clean Google Web Risk scan. This indicates diligent efforts to protect user connections and data from common threats.

Identity 80/100

This domain boasts nearly three decades of existence, clearly establishing its long-term presence. Although it lacks a favicon and the domain renewal date is a bit close, its registration through 'get.gov' reinforces its official status.

Reputation 75/100

Its very high Tranco rank confirms widespread recognition and trust. However, the site's current HTTP 403 status is a significant operational issue that detracts from an otherwise excellent reputation.

Transparency 60/100

A major legislative resource should make it effortless for citizens to get in touch. The absence of easily discoverable contact information and social media links on the homepage is a notable oversight.

Compliance 40/100

The complete absence of a privacy policy and terms of service is a significant compliance gap. For a government website handling public information, this is a serious concern that must be addressed.

Infrastructure 90/100

The underlying infrastructure is robust, with multiple IP addresses, properly configured email authentication (SPF, DMARC), and DNSSEC. This indicates a well-managed and resilient technical foundation.

Signals Detected

[+]
Tranco Rank: Rank #2472

This is a well-known, high-traffic website

[?]
Structured Data: None found

No structured data markup found

[?]
Trustpilot: No Trustpilot profile

This business has no Trustpilot presence — not unusual for smaller or newer companies

[~]
Branding: Missing

No favicon found — unusual for an established business

[+]
SSL Certificate: Valid

Valid certificate, expires in 63 days

[?]
Certificate Issuer: Google Trust Services

Certificate issued by Google Trust Services

[+]
TLS Version: TLS 1.3

Connection uses TLS 1.3

[?]
Certificate Transparency: Unable to check

crt.sh returned status 429

[+]
Clickjacking Protection: Present

X-Frame-Options: SAMEORIGIN

[?]
Server: cloudflare

Web server: cloudflare

[+]
Google Web Risk: Clean

No threats detected by Google Web Risk

[?]
Sitemap: Not found

No sitemap found — common for smaller sites

[+]
DNS Resolution: 4 IP(s)

Resolves to: 2a06:98c1:310a::6812:2b32, 2a06:98c1:310d::ac40:90ce, 172.64.144.206, 104.18.43.50

[+]
Email (MX Records): 4 record(s)

Mail servers: mx22.loc.gov., mx41.loc.gov., mx23.loc.gov., mx42.loc.gov.

[+]
SPF Record: Present

Domain has SPF email authentication configured

[+]
DMARC Record: Present

Domain has DMARC email authentication configured

[+]
Name Servers: 2 server(s)

DNS providers: alice.ns.cloudflare.com., kevin.ns.cloudflare.com.

[~]
Website Status: HTTP 403

Website returned status 403

[~]
Contact Info: Not found

No obvious contact information found on homepage

[-]
Legal Pages: Missing

No privacy policy or terms of service found

[~]
Social Media Presence: None found

No social media links found on homepage

[+]
robots.txt: Present

robots.txt has 143 directives and references a sitemap

[+]
DNS Blacklists: Clean

Not found on any DNS blacklists

[+]
Domain Age: 28 years, 11 months

Domain created 1997-10-02T01:29:22Z (28 years, 11 months ago)

[?]
Registrar: get.gov

Registered through get.gov

[~]
Domain Expiry: 2026-07-07T17:47:38Z

Expires in 80 days

[+]
DNSSEC: signedDelegation

DNSSEC status from WHOIS

[?]
Web Archive: Unable to check

Could not query Wayback Machine

[+]
Page Load Time: 41ms

Fast page load

Embed This Badge

Own this site? Show visitors your trust score.

Trust badge for congress.gov
<a href="https://verified.fyi/review/congress.gov"><img src="https://verified.fyi/badge/congress.gov?size=medium&style=full&theme=dark" alt="congress.gov trust score — verified.fyi" /></a>
[![congress.gov trust score](https://verified.fyi/badge/congress.gov?size=medium&style=full&theme=dark)](https://verified.fyi/review/congress.gov)

Stay Safe Online

Good habits to protect yourself, no matter the scan result.

Use a password manager

Never reuse passwords across sites.

Enable two-factor authentication

Add a second layer of security to your accounts.

Check before you buy

Always verify unfamiliar stores before entering payment info.

When evaluating a governmental website like congress.gov, the expectations for transparency and reliability are incredibly high. For a site designed to provide legislative information to the public, clarity and accessibility are paramount, and any deviation can raise questions. While this site holds excellent foundational elements – a domain almost 30 years old, a top global ranking confirming its high traffic, and robust security protocols like TLS 1.3 – there are surprising omissions. Most legitimate government portals prioritize easy citizen engagement. Oddly, congress.gov doesn't readily display contact information or link to social media profiles from its homepage, making it harder for users to connect or seek help. This is a crucial element that citizens expect from a public service platform. Perhaps the most concerning aspect for a site of this nature is the lack of visible legal pages, specifically a privacy policy and terms of service. For a platform that collects and presents legislative data, providing clear statements on data handling and user expectations isn't just good practice—it's often a legal requirement and a fundamental building block of public trust. While its technical backend is solid, these user-facing gaps mean congress.gov, despite its official status, doesn't meet all the trust signals one would anticipate from a leading government resource.