Correct a description, link or other detail. Submissions are reviewed before publication.
Lifeline · velvik.ru over time
Checked in the last 30 daysOlder, dated recordFrom registration records
One registrar since Apr 6, 2024 · no registrant change on record since 2024 · last checked Aug 17, 2026.
Registration
No registration date on file yet. AboutUs reads it from RDAP when the site is checked.
AboutUs record
Current AboutUs recordJul 18, 2026 – Aug 17, 2026 (latest)Authority and Safety last refreshed Aug 17, 2026.Source: AboutUs checks
Registrar
RU-CENTER-RURU-CENTER-RUApr 6, 2024 – Jan 16, 2026 (latest)Registrar RU-CENTER-RU in the WHOIS and RDAP records held for velvik.ru, from Apr 6, 2024 to Jan 16, 2026.Source: WHOIS / RDAP archive (who.is)
Registrant
Registrant recordsApr 6, 2024 – Jan 16, 2026Registration records for velvik.ru are held from Apr 6, 2024 to Jan 16, 2026 (6 records). None shows a change of registrant. Privacy-service and redaction changes, renames of the same organization and new contacts at it are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
No registrant changes recorded, 2024–2026
Zone file
No nameserver records held, Jan 2026 – Nov 2026Nameservers: velvik.ruNameservers: velvik.ruApr 6, 2024 – Jan 16, 2026Registration records listed velvik.ru nameservers (ns-151.velvik.ru, ns-235.velvik.ru) for velvik.ru from Apr 6, 2024 to Jan 16, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
Certificate
Let's EncryptNov 13, 2026 – Nov 20, 2026Let's Encrypt issued 1 certificate for velvik.ru from Nov 13, 2026, the latest valid until Feb 11, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
2025Jan ’26Jul ’26← last 12 months, drawn wider
Every dated fact on this lifeline (5)
Apr 6, 2024 – Jan 16, 2026Registrar: Registrar RU-CENTER-RU in the WHOIS and RDAP records held for velvik.ru, from Apr 6, 2024 to Jan 16, 2026.Source: WHOIS / RDAP archive (who.is)
Apr 6, 2024 – Jan 16, 2026Registrant: Registration records for velvik.ru are held from Apr 6, 2024 to Jan 16, 2026 (6 records). None shows a change of registrant. Privacy-service and redaction changes, renames of the same organization and new contacts at it are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Apr 6, 2024 – Jan 16, 2026Zone file: Registration records listed velvik.ru nameservers (ns-151.velvik.ru, ns-235.velvik.ru) for velvik.ru from Apr 6, 2024 to Jan 16, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
Jul 18, 2026 – Aug 17, 2026AboutUs record: Authority and Safety last refreshed Aug 17, 2026.Source: AboutUs checks
Nov 13, 2026 – Nov 20, 2026Certificate: Let's Encrypt issued 1 certificate for velvik.ru from Nov 13, 2026, the latest valid until Feb 11, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
3 of 4 safety checks passed (Nov 20, 2026).
Site is live · HTTPS valid
velvik.ru has an AboutUs profile for public website intelligence, ownership context, trust signals, monitoring, and owner verification.
Add the HSTS, Content-Security-Policy, and X-Frame-Options response headers.
AboutUs has not vetted this site. Everything below is what we could measure automatically. Anything you do on the site — paying, sharing personal details, downloading — is between you and the site, not AboutUs.
Current facts
Latest available measurements; dated entries retain their dates. These are measurements, not an endorsement of the site.
not yet retrieved
Registrar and registration date not retrieved yet — we retry on every view.
We withhold an authority number until independent evidence (global rank, link-graph presence) has accrued. The facts we do have about this site are shown below — we'd rather say “not enough signals yet” than invent a low score.
Safety evidence
No unexpired threat-feed result; name-similarity check available (recorded about 94 days ago); 3/3 transport and email checks available (oldest recorded about 94 days ago). This is evidence coverage, not a probability that a website is safe.
Recorded HTTPS check did not confirm a valid connection
Missing DMARC (mild)
Site history
Dated record — historical facts always carry their date.