namu.wiki

#432A82AE · Very Safe
95 / 100
SentryRating · namu.wiki — Report card
104.16.219.109 Valid HTTPS 11.1 years Dynadot Inc Updated

How trustworthy is namu.wiki?

namu.wiki resolves to a server in Unknown. Here is what its public records and certificates reveal.

Technical Information

IP Address
104.16.219.109
Server Location
Unknown
ISP / Provider
Unknown

SSL Certificate

SSL Certificate
Valid HTTPS
SSL Issuer
WE1
Valid Until
2026-06-10

Registrar

Registrar
Dynadot Inc
Registered On
2015-04-11
Expires On
2031-04-11
Domain Age
11.1 years

Initial findings

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

Registration history

namu.wiki has existed for about 11.1 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 namu.wiki 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 namu.wiki is processed on servers located in Unknown. Choose to share data accordingly.

Risk perspective

Domains with the profile of namu.wiki (age 11.1 years, SSL OK, registrar Dynadot Inc, country Unknown) usually fall in the "very_safe" category in our automated scoring.

Verdict

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

Frequently Asked Questions

Does namu.wiki use HTTPS?
The HTTPS handshake returned: OK.
What is the registration date of namu.wiki?
namu.wiki has existed for about 11.1 years according to RDAP.
Where was namu.wiki bought?
According to RDAP data, namu.wiki was registered through Dynadot Inc.
What goes into the namu.wiki trust rating?
We mix four ingredients: domain age, certificate state, registrar reputation and DNS health, and project the result onto a 0-100 scale.
Is the WHOIS information about namu.wiki hidden?
Privacy services hide the registrant — this is normal and not a red flag in itself.

What looks good

  • Returns valid SOA and TXT records
  • Registered with an established registrar
  • Consistent name-server configuration
  • WHOIS data accessible (privacy-protected or full)

What to watch

  • No HSTS header detected at the apex
  • Name-servers belong to the same registrar (no diversity)
  • Always verify content before transacting

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 →