tufs.ac.jp

#FBA25086 · Moderate
45 / 100
TraceSentry · tufs.ac.jp — Report card
Japan 202.13.5.157 No HTTPS Updated

tufs.ac.jp safety overview

Public records for tufs.ac.jp stretch back about ? years. Combined with the live SSL status, they form the basis of our trust score.

Technical Information

IP Address202.13.5.157
Server LocationJapan · Fuchū
ISP / ProviderUnknown
SSL Certificate No HTTPS
RegistrarUnknown

Initial findings

Our automated probe of tufs.ac.jp returned a clean DNS answer pointing to Japan, served by Unknown, with the TLS handshake responding No.

HTTPS verdict

Our HTTPS probe to tufs.ac.jp concluded with: No. Together with the registrar and hosting country, this forms the security side of the scorecard.

Registration history

tufs.ac.jp has existed for about ? years. Long-lived domains are usually associated with established projects, although age alone is not a guarantee of safety.

Where the data lives

Anything you submit to tufs.ac.jp is processed on servers located in Japan. Choose to share data accordingly.

Risk perspective

Domains with the profile of tufs.ac.jp (age ? years, SSL No, registrar Unknown, country Japan) usually fall in the "moderate" category in our automated scoring.

Verdict

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

Frequently Asked Questions

What looks risky about tufs.ac.jp?
For tufs.ac.jp we look at: age ? yrs, SSL No, registrar Unknown and hosting in Japan. Any single weak point can drag the technical confidence down.
How often is tufs.ac.jp 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 tufs.ac.jp?
The current network announcement comes from Unknown, with the IP geo-located in Japan.
Where do I file a complaint about tufs.ac.jp?
You can file a takedown notice with the registrar (Unknown) or the hosting ISP (Unknown). Each maintains a public abuse channel.

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