ntsb.gov

Item: ntsb.gov
Rating: 4.8
Author: AnalyzeDesk

#F67A6996 · Very Safe

95 / 100

104.18.20.78 Valid HTTPS 28.7 years get.gov Updated 14 days ago

ntsb.gov — what the public records say

Our trust engine inspected ntsb.gov on Unknown hosting, registrar (get.gov) and SSL state. The takeaways are summarised here.

IP Address · Server Location

104.18.20.78

Unknown

SSL Certificate

Valid HTTPS

WE1

Valid Until: 2026-09-06

Registrar

get.gov

Registered On: 1997-10-02

28.7 years

Very Safe

95/100

Verdict at a glance

Initial findings

Our automated probe of ntsb.gov returned a clean DNS answer pointing to Unknown, served by Unknown, with the TLS handshake responding OK.

Registration history

ntsb.gov has existed for about 28.7 years. Long-lived domains are usually associated with established projects, although age alone is not a guarantee of safety.

HTTPS verdict

Our HTTPS probe to ntsb.gov concluded with: OK. Together with the registrar and hosting country, this forms the security side of the scorecard.

Where the data lives

Anything you submit to ntsb.gov is processed on servers located in Unknown. Choose to share data accordingly.

Risk perspective

Domains with the profile of ntsb.gov (age 28.7 years, SSL OK, registrar get.gov, country Unknown) usually fall in the "very_safe" category in our automated scoring.

Verdict

Trust score: 95/100 — very_safe. This is an automated, technical-only verdict; treat it as one data point among many.

What looks good

Several years of registration history
No malware signature triggered our quick scan
Hosting country aligns with stated audience
Resolves over public recursive DNS (Google, Cloudflare, Quad9)

What to watch

Name-servers belong to the same registrar (no diversity)
Always verify content before transacting
No independent third-party reviews available

Related Domains

Frequently Asked Questions

Is ntsb.gov a phishing website?

Our scanner does not perform visual similarity checks. We can only confirm that no obvious infrastructure markers (cert mismatch, fresh registration with high traffic) were triggered.

What looks risky about ntsb.gov?

For ntsb.gov we look at: age 28.7 yrs, SSL OK, registrar get.gov and hosting in Unknown. Any single weak point can drag the technical confidence down.

How often is ntsb.gov re-checked?

By default the report is refreshed every 30 days, plus on every manual re-check from the dashboard.

Is the score enough to decide?

A high score is necessary but not sufficient. Always pair the report with a content-level sanity check before transacting.

What ISP serves ntsb.gov?

The current network announcement comes from Unknown, with the IP geo-located in Unknown.

This report is generated automatically from public technical signals. It is not legal or financial advice.

Vet your next domain in under 10 seconds.

No signup. No credit card. No hidden quotas.

Start a free check →