Report ID: #D42E6C20

stthomasphiladelphia.org

United States Valid HTTPS 20.8 years Updated
100
Very Safe
VividAnalyze · stthomasphiladelphia.org — Report card
VividAnalyze · stthomasphiladelphia.org

Quick verdict on stthomasphiladelphia.org

A frequent question we get is "how safe is stthomasphiladelphia.org?". We computed an automated answer using only public data — see below.

Technical Information

IP Address162.241.24.245
Server LocationUnited States · Phoenix
ISP / ProviderUnknown
SSL Certificate Valid HTTPS
SSL IssuerR12
Valid Until2026-08-05
RegistrarGoDaddy.com, LLC
Registered On2005-08-10
Expires On2033-08-10
Domain Age20.8 years

Public-record summary

From the public records linked to stthomasphiladelphia.org we extracted four anchors: country United States, registrar GoDaddy.com, LLC, age 20.8 yrs, encryption status OK. Everything else builds on those.

How long has stthomasphiladelphia.org existed?

According to RDAP records, stthomasphiladelphia.org was registered around 20.8 years ago through GoDaddy.com, LLC. This is a useful signal but should be combined with content review.

In-transit protection

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

Infrastructure provider

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

How we read this profile

For stthomasphiladelphia.org, the combined picture (20.8 yrs, SSL OK, United States hosting, GoDaddy.com, LLC registration) lands in the "very_safe" band. That is a starting point, not a final verdict.

Final take

Combining all signals, we rate stthomasphiladelphia.org at 100/100 (very_safe). Always perform your own due diligence before sharing personal data or money.

What looks good

  • Stable IPv4 hosting
  • Public RDAP record available
  • TLS supports modern cipher suites
  • Stable name-servers across NS records

What to watch

  • Limited public reputation data
  • No HSTS header detected at the apex
  • Name-servers belong to the same registrar (no diversity)

Frequently Asked Questions

Is stthomasphiladelphia.org safe for online payments?
Infrastructure check returned SSL OK and a "very_safe" score. This is a baseline; never enter card data on a site you have not verified through other channels.
What lowered stthomasphiladelphia.org's score?
stthomasphiladelphia.org sits at the lower band when at least one of these is true: SSL OK is failing, age 20.8 years is short, registrar GoDaddy.com, LLC is unknown, or country United States does not match the audience.
Is stthomasphiladelphia.org safe to use?
We did not find blocklist hits or obvious infrastructure red flags for stthomasphiladelphia.org. That is a baseline signal, not a final verdict.
What jurisdiction handles stthomasphiladelphia.org?
stthomasphiladelphia.org is operated from United States through Unknown.
Is stthomasphiladelphia.org encrypted?
When we tried to connect over HTTPS to stthomasphiladelphia.org the result was: OK.

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 →