kcm.fm

#BAF4F817 · Very Safe
95 / 100
ArrowJudge · kcm.fm — Report card
172.67.162.204 Valid HTTPS 8.5 years dotFM Updated

Open inspection of kcm.fm

This page summarises the technical signals collected for kcm.fm: server location, HTTPS status, registrar, domain age and DNS configuration.

Initial findings

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

Registration history

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

Risk perspective

Domains with the profile of kcm.fm (age 8.5 years, SSL OK, registrar dotFM, 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.

What looks good

  • TLS supports modern cipher suites
  • Stable name-servers across NS records
  • Properly configured DNS records
  • Has MX records (capable of email)

What to watch

  • Uses generic shared hosting (cannot identify operator from IP)
  • TXT records expose minimal trust hints
  • TLS configuration accepts older cipher suites

Frequently Asked Questions

Is the WHOIS information about kcm.fm hidden?
Most modern registrars apply privacy protection by default, so personal contact data may be redacted. Registration dates and registrar are still visible.
Is kcm.fm on a security blocklist?
At the time of audit, kcm.fm was not present in the public blocklists we sample (PhishTank, abuse feeds, etc.).
Is kcm.fm 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 kcm.fm?
For kcm.fm we look at: age 8.5 yrs, SSL OK, registrar dotFM and hosting in Unknown. Any single weak point can drag the technical confidence down.
How often is kcm.fm re-checked?
By default the report is refreshed every 30 days, plus on every manual re-check from the dashboard.

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 →