Correct a description, link or other detail. Submissions are reviewed before publication.
Lifeline · warnet.ws over time
Checked in the last 30 daysOlder, dated recordFrom registration records
On AboutUs since 2007 · 1 registrar change since Jan 16, 2009 · 5 registrant changes since 2009 · last checked Oct 17, 2026.
Registration
No registration date on file yet. AboutUs reads it from RDAP when the site is checked.
AboutUs record
AboutUs wiki pageJul 7, 2007An AboutUs wiki page described warnet.ws from Jul 7, 2007 to Jul 7, 2007 (1 edit).Source: AboutUs wiki archive, 2006–2023Current AboutUs recordJun 27, 2026 – Oct 17, 2026 (latest)Authority and Safety last refreshed Oct 17, 2026.Source: AboutUs checks
Registrar
Regtime.net Ltd.Jan 16, 2009 – Feb 16, 2009Registrar Regtime.net Ltd. in the WHOIS and RDAP records held for warnet.ws, from Jan 16, 2009 to Feb 16, 2009.Source: WHOIS / RDAP archive (who.is)REGTIME LTD.
Registrant
Registrant recordsJan 16, 2009 – Jun 26, 2026Registration records for warnet.ws are held from Jan 16, 2009 to Jun 26, 2026 (203 records). 5 changes of registrant name or organization are marked. 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
Zone file
No nameserver records held, Dec 2013 – Jun 2016Nameservers: icqlog.ruMar 7, 2009 – Oct 20, 2010Registration records listed icqlog.ru nameservers (ns1.icqlog.ru, ns2.icqlog.ru) for warnet.ws from Mar 7, 2009 to Oct 20, 2010.Source: From registration records (WHOIS / RDAP archive, who.is)
Certificate
Google Trust ServicesApr 3, 2026 – Nov 13, 2026Google Trust Services issued 5 certificates for warnet.ws from Apr 3, 2026, the latest valid until Dec 27, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
2010201520202025Apr ’26← last 12 months, drawn wider
Every dated fact on this lifeline (19)
Jul 7, 2007AboutUs record: An AboutUs wiki page described warnet.ws from Jul 7, 2007 to Jul 7, 2007 (1 edit).Source: AboutUs wiki archive, 2006–2023
Jan 16, 2009 – Feb 16, 2009Registrar: Registrar Regtime.net Ltd. in the WHOIS and RDAP records held for warnet.ws, from Jan 16, 2009 to Feb 16, 2009.Source: WHOIS / RDAP archive (who.is)
Jan 16, 2009 – Jun 26, 2026Registrant: Registration records for warnet.ws are held from Jan 16, 2009 to Jun 26, 2026 (203 records). 5 changes of registrant name or organization are marked. 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
Mar 7, 2009 – Jun 26, 2026Registrar: Registrar REGTIME LTD. (IANA 1362) in the WHOIS and RDAP records held for warnet.ws, from Mar 7, 2009 to Jun 26, 2026.Source: WHOIS / RDAP archive (who.is)
Mar 7, 2009Registrant: The registrant name or organization in the registration record changed; first recorded Mar 7, 2009. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
REGTIME LTD.
Mar 7, 2009 – Jun 26, 2026 (latest)
Registrar REGTIME LTD. (IANA 1362) in the WHOIS and RDAP records held for warnet.ws, from Mar 7, 2009 to Jun 26, 2026.
Source: WHOIS / RDAP archive (who.is)
Registrant changeMar 7, 2009The registrant name or organization in the registration record changed; first recorded Mar 7, 2009. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Registrant changeJun 22, 2019The registrant name or organization in the registration record changed; first recorded Jun 22, 2019. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Registrant changeSep 17, 2020The registrant name or organization in the registration record changed; first recorded Sep 17, 2020. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Registrant changeNov 17, 2020The registrant name or organization in the registration record changed; first recorded Nov 17, 2020. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Registrant changeNov 23, 2021The registrant name or organization in the registration record changed; first recorded Nov 23, 2021. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
5 registrant changes, 2009–2026
Nameservers: nameself.comNov 9, 2010 – Dec 26, 2013Registration records listed nameself.com nameservers (ns1.nameself.com, ns2.nameself.com) for warnet.ws from Nov 9, 2010 to Dec 26, 2013.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to nameself.comNov 9, 2010warnet.ws's nameservers moved from icqlog.ru to nameself.com between Oct 20, 2010 and Nov 9, 2010. Last seen at icqlog.ru: Oct 20, 2010 (registration record). First seen at nameself.com: Nov 9, 2010 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Nameservers: fornex.comJun 28, 2016 – Feb 20, 2017Registration records listed fornex.com nameservers (ns1.fornex.com, ns2.fornex.com, ns3.fornex.com…) for warnet.ws from Jun 28, 2016 to Feb 20, 2017.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to fornex.comJun 28, 2016warnet.ws's nameservers moved from nameself.com to fornex.com at some point between Dec 26, 2013 and Jun 28, 2016. Last seen at nameself.com: Dec 26, 2013 (registration record). First seen at fornex.com: Jun 28, 2016 (registration record). AboutUs holds no nameserver records for the about 3 years in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Nameservers: CloudflareNameservers: CloudflareAug 16, 2017 – Jun 26, 2026Registration records listed Cloudflare nameservers (brenda.ns.cloudflare.com, chad.ns.cloudflare.com) for warnet.ws from Aug 16, 2017 to Jun 26, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to CloudflareAug 16, 2017warnet.ws's nameservers moved from fornex.com to Cloudflare at some point between Feb 20, 2017 and Aug 16, 2017. Last seen at fornex.com: Feb 20, 2017 (registration record). First seen at Cloudflare: Aug 16, 2017 (registration record). AboutUs holds no nameserver records for the 6 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Let's Encrypt
Apr 18, 2026 – Nov 13, 2026 (latest)
Let's Encrypt issued 12 certificates for warnet.ws from Apr 18, 2026, the latest valid until Feb 10, 2027. Seen in use on Oct 5, 2026.
Source: Certificate Transparency logs (AboutUs's own certificate-log reader); TLS check, Oct 5, 2026
Mar 7, 2009 – Oct 20, 2010
Zone file: Registration records listed icqlog.ru nameservers (ns1.icqlog.ru, ns2.icqlog.ru) for warnet.ws from Mar 7, 2009 to Oct 20, 2010.Source: From registration records (WHOIS / RDAP archive, who.is)
Nov 9, 2010 – Dec 26, 2013Zone file: Registration records listed nameself.com nameservers (ns1.nameself.com, ns2.nameself.com) for warnet.ws from Nov 9, 2010 to Dec 26, 2013.Source: From registration records (WHOIS / RDAP archive, who.is)
Nov 9, 2010Zone file: warnet.ws's nameservers moved from icqlog.ru to nameself.com between Oct 20, 2010 and Nov 9, 2010. Last seen at icqlog.ru: Oct 20, 2010 (registration record). First seen at nameself.com: Nov 9, 2010 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Jun 28, 2016 – Feb 20, 2017Zone file: Registration records listed fornex.com nameservers (ns1.fornex.com, ns2.fornex.com, ns3.fornex.com…) for warnet.ws from Jun 28, 2016 to Feb 20, 2017.Source: From registration records (WHOIS / RDAP archive, who.is)
Jun 28, 2016Zone file: warnet.ws's nameservers moved from nameself.com to fornex.com at some point between Dec 26, 2013 and Jun 28, 2016. Last seen at nameself.com: Dec 26, 2013 (registration record). First seen at fornex.com: Jun 28, 2016 (registration record). AboutUs holds no nameserver records for the about 3 years in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Aug 16, 2017 – Jun 26, 2026Zone file: Registration records listed Cloudflare nameservers (brenda.ns.cloudflare.com, chad.ns.cloudflare.com) for warnet.ws from Aug 16, 2017 to Jun 26, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
Aug 16, 2017Zone file: warnet.ws's nameservers moved from fornex.com to Cloudflare at some point between Feb 20, 2017 and Aug 16, 2017. Last seen at fornex.com: Feb 20, 2017 (registration record). First seen at Cloudflare: Aug 16, 2017 (registration record). AboutUs holds no nameserver records for the 6 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Jun 22, 2019Registrant: The registrant name or organization in the registration record changed; first recorded Jun 22, 2019. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Sep 17, 2020Registrant: The registrant name or organization in the registration record changed; first recorded Sep 17, 2020. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Nov 17, 2020Registrant: The registrant name or organization in the registration record changed; first recorded Nov 17, 2020. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Nov 23, 2021Registrant: The registrant name or organization in the registration record changed; first recorded Nov 23, 2021. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Apr 3, 2026 – Nov 13, 2026Certificate: Google Trust Services issued 5 certificates for warnet.ws from Apr 3, 2026, the latest valid until Dec 27, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Apr 18, 2026 – Nov 13, 2026Certificate: Let's Encrypt issued 12 certificates for warnet.ws from Apr 18, 2026, the latest valid until Feb 10, 2027. Seen in use on Oct 5, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader); TLS check, Oct 5, 2026
Jun 27, 2026 – Oct 17, 2026AboutUs record: Authority and Safety last refreshed Oct 17, 2026.Source: AboutUs checks
1 of 2 safety checks passed (Nov 13, 2026).
AboutUs could not get a response over HTTPS when it checked (Nov 13, 2026)
warnet.ws has an AboutUs profile for public website intelligence, ownership context, trust signals, monitoring, and owner verification.
Make sure the site responds over HTTPS with a valid certificate.
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 26 days ago); 3/3 transport and email checks available (oldest recorded about 26 days ago). This is evidence coverage, not a probability that a website is safe.
Missing DMARC (mild)
Site history
Dated record — historical facts always carry their date.