example.edu

#33D2CA7B · Safe
65 / 100
AddressEndpoint · example.edu — Report card
104.20.35.130 Valid HTTPS Updated

Reading the signals of example.edu

The numbers below come straight from example.edu's live DNS, TLS and RDAP responses. We do not store editorial opinions.

Technical Information

IP Address
104.20.35.130
Server Location
Unknown
ISP / Provider
Unknown

SSL Certificate

SSL Certificate
Valid HTTPS
SSL Issuer
WE1
Valid Until
2026-08-28

Registrar

Registrar
Unknown

Public-record summary

From the public records linked to example.edu we extracted four anchors: country Unknown, registrar Unknown, age ? yrs, encryption status OK. Everything else builds on those.

In-transit protection

For data moving between the user and example.edu, the encryption check returned: OK. This is the single most important infrastructural safety check we run.

How long has example.edu existed?

According to RDAP records, example.edu was registered around ? years ago through Unknown. This is a useful signal but should be combined with content review.

Infrastructure provider

Our GeoIP lookup places example.edu on the Unknown network, geographically in Unknown. ISP-level reputation matters: established networks tend to act on abuse reports faster.

How we read this profile

For example.edu, the combined picture (? yrs, SSL OK, Unknown hosting, Unknown registration) lands in the "safe" band. That is a starting point, not a final verdict.

Final take

Combining all signals, we rate example.edu at 65/100 (safe). Always perform your own due diligence before sharing personal data or money.

Frequently Asked Questions

What goes into the example.edu 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 example.edu hidden?
Privacy services hide the registrant — this is normal and not a red flag in itself.
Is example.edu on a security blocklist?
Our quick lookup against common public blocklists did not return a hit for example.edu at the time of this report.
Is example.edu 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 example.edu?
For example.edu we look at: age ? yrs, SSL OK, registrar Unknown and hosting in Unknown. Any single weak point can drag the technical confidence down.

What looks good

  • Public RDAP record available
  • TLS supports modern cipher suites
  • Stable name-servers across NS records
  • Properly configured DNS records

What to watch

  • Privacy-protected WHOIS — operator not directly visible
  • Registrar based outside the target audience country
  • No corporate footprint linked to the domain

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 →