220.lv

#5CC820BB · Safe
65 / 100
VividUrl · 220.lv — Report card
104.16.176.135 Valid HTTPS Updated

220.lv — full safety report

Below you will find an independent technical breakdown of 220.lv, gathered from public infrastructure data with no human bias.

Technical Information

IP Address
104.16.176.135
Server Location
Unknown
ISP / Provider
Unknown

SSL Certificate

SSL Certificate
Valid HTTPS
SSL Issuer
RapidSSL TLS RSA CA G1
Valid Until
2026-09-07

Registrar

Registrar
Unknown

Initial findings

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

HTTPS verdict

Our HTTPS probe to 220.lv concluded with: OK. Together with the registrar and hosting country, this forms the security side of the scorecard.

Registration history

220.lv 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 220.lv is processed on servers located in Unknown. Choose to share data accordingly.

Risk perspective

Domains with the profile of 220.lv (age ? years, SSL OK, registrar Unknown, country Unknown) usually fall in the "safe" category in our automated scoring.

Verdict

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

Frequently Asked Questions

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

What looks good

  • No malware signature triggered our quick scan
  • Hosting country aligns with stated audience
  • Resolves over public recursive DNS (Google, Cloudflare, Quad9)
  • Uses modern HTTPS endpoints

What to watch

  • No structured Schema.org metadata published
  • Hosting on a residential/dynamic IP block
  • Technical signals alone cannot prove ownership

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 →