Correct a description, link or other detail. Submissions are reviewed before publication.
Lifeline · cocktailteam.net over time
Checked in the last 30 daysOlder, dated recordFrom registration records
Registered 22 years ago · on AboutUs since 2007 · 3 registrar changes since Mar 24, 2014 · 2 registrant changes since 2014 · last checked Sep 20, 2026.
Registration
RegisteredJul 21, 2004cocktailteam.net was registered on Jul 21, 2004.Source: RDAP, fetched Sep 20, 2026
AboutUs record
AboutUs wiki pageAboutUs wiki pageJan 11, 2007 – Nov 7, 2013An AboutUs wiki page described cocktailteam.net from Jan 11, 2007 to Nov 7, 2013 (2 edits).Source: AboutUs wiki archive, 2006–2023
Registrar
ENOM, INC.ENOM, INC.Mar 24, 2014 – Mar 20, 2021Registrar ENOM, INC. (IANA 48) in the WHOIS and RDAP records held for cocktailteam.net, from Mar 24, 2014 to Mar 20, 2021.Source: WHOIS / RDAP archive (who.is)
Registrant
Registrant recordsMar 24, 2014 – Jun 18, 2026Registration records for cocktailteam.net are held from Mar 24, 2014 to Jun 18, 2026 (65 records). 2 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
Nameservers: wtservers.comOct 18, 2013 – Apr 1, 2016wtservers.com (ns1.wtservers.com, ns2.wtservers.com) were the nameservers listed for cocktailteam.net at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Apr 1, 2016 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Certificate
Sectigo LimitedFeb 24, 2026 – Nov 19, 2026Sectigo Limited issued 1 certificate for cocktailteam.net from Feb 24, 2026, the latest valid until Feb 24, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)Let's Encrypt
20052010201520202025Apr ’26← last 12 months, drawn wider
Every dated fact on this lifeline (20)
Jul 21, 2004Registration: cocktailteam.net was registered on Jul 21, 2004.Source: RDAP, fetched Sep 20, 2026
Jan 11, 2007 – Nov 7, 2013AboutUs record: An AboutUs wiki page described cocktailteam.net from Jan 11, 2007 to Nov 7, 2013 (2 edits).Source: AboutUs wiki archive, 2006–2023
Oct 18, 2013 – Apr 1, 2016Zone file: wtservers.com (ns1.wtservers.com, ns2.wtservers.com) were the nameservers listed for cocktailteam.net at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Apr 1, 2016 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Mar 24, 2014 – Mar 20, 2021Registrar: Registrar ENOM, INC. (IANA 48) in the WHOIS and RDAP records held for cocktailteam.net, from Mar 24, 2014 to Mar 20, 2021.Source: WHOIS / RDAP archive (who.is)
Mar 24, 2014 – Jun 18, 2026Registrant: Registration records for cocktailteam.net are held from Mar 24, 2014 to Jun 18, 2026 (65 records). 2 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
Current AboutUs record
Jul 18, 2026 – Aug 18, 2026 (latest)
Authority and Safety last refreshed Aug 18, 2026.
Source: AboutUs checks
OVH, SAS
Apr 20, 2021 – Feb 21, 2022
Registrar OVH, SAS (IANA 433) in the WHOIS and RDAP records held for cocktailteam.net, from Apr 20, 2021 to Feb 21, 2022.
Source: WHOIS / RDAP archive (who.is)
FastDomain Inc.FastDomain Inc.Apr 16, 2022 – Jun 18, 2026Registrar FastDomain Inc. (IANA 1154) in the WHOIS and RDAP records held for cocktailteam.net, from Apr 16, 2022 to Jun 18, 2026.Source: WHOIS / RDAP archive (who.is)
Bluehost Inc.Sep 20, 2026 – Oct 20, 2026 (latest)Registrar Bluehost Inc. in the registration data recorded, first on Sep 20, 2026 and most recently on Oct 20, 2026.Source: RDAP, fetched Sep 20, 2026
Registrant changeApr 16, 2022The registrant name or organization in the registration record changed; first recorded Apr 16, 2022. 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 15, 2023The registrant name or organization in the registration record changed; first recorded Nov 15, 2023. 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
2 registrant changes, 2014–2026
Nameservers: mydnspt.netSep 3, 2016 – Apr 3, 2018mydnspt.net (ns1.mydnspt.net, ns2.mydnspt.net, ns7.mydnspt.net…) were the nameservers listed for cocktailteam.net at every ICANN zone-file snapshot AboutUs holds from Sep 3, 2016 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
DNS moved to mydnspt.netSep 3, 2016cocktailteam.net's nameservers moved from wtservers.com to mydnspt.net at some point between Apr 1, 2016 and Sep 3, 2016. Last seen at wtservers.com: Apr 1, 2016 (ICANN zone-file snapshot). First seen at mydnspt.net: Sep 3, 2016 (ICANN zone-file snapshot). AboutUs holds no nameserver records for the 5 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (ICANN zone-file snapshot → ICANN zone-file snapshot)
Nameservers: mydnspt.netAug 1, 2018 – Mar 20, 2021Registration records listed mydnspt.net nameservers (ns1.mydnspt.net, ns2.mydnspt.net, ns7.mydnspt.net…) for cocktailteam.net from Aug 1, 2018 to Mar 20, 2021.Source: From registration records (WHOIS / RDAP archive, who.is)
Nameservers: ovh.netApr 20, 2021 – Feb 21, 2022Registration records listed ovh.net nameservers (dns13.ovh.net, ns13.ovh.net) for cocktailteam.net from Apr 20, 2021 to Feb 21, 2022.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to ovh.netApr 20, 2021cocktailteam.net's nameservers moved from mydnspt.net to ovh.net between Mar 20, 2021 and Apr 20, 2021. Last seen at mydnspt.net: Mar 20, 2021 (registration record). First seen at ovh.net: Apr 20, 2021 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Nameservers: bluehost.comNameservers: bluehost.comApr 16, 2022 – Jun 18, 2026Registration records listed bluehost.com nameservers (ns1.bluehost.com, ns2.bluehost.com) for cocktailteam.net from Apr 16, 2022 to Jun 18, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to bluehost.comApr 16, 2022cocktailteam.net's nameservers moved from ovh.net to bluehost.com at some point between Feb 21, 2022 and Apr 16, 2022. Last seen at ovh.net: Feb 21, 2022 (registration record). First seen at bluehost.com: Apr 16, 2022 (registration record). AboutUs holds no nameserver records for the 54 days 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)
Mar 23, 2026 – Nov 19, 2026
Let's Encrypt issued 22 certificates for cocktailteam.net from Mar 23, 2026, the latest valid until Feb 5, 2027.
Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Sep 3, 2016 – Apr 3, 2018
Zone file: mydnspt.net (ns1.mydnspt.net, ns2.mydnspt.net, ns7.mydnspt.net…) were the nameservers listed for cocktailteam.net at every ICANN zone-file snapshot AboutUs holds from Sep 3, 2016 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Sep 3, 2016Zone file: cocktailteam.net's nameservers moved from wtservers.com to mydnspt.net at some point between Apr 1, 2016 and Sep 3, 2016. Last seen at wtservers.com: Apr 1, 2016 (ICANN zone-file snapshot). First seen at mydnspt.net: Sep 3, 2016 (ICANN zone-file snapshot). AboutUs holds no nameserver records for the 5 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (ICANN zone-file snapshot → ICANN zone-file snapshot)
Aug 1, 2018 – Mar 20, 2021Zone file: Registration records listed mydnspt.net nameservers (ns1.mydnspt.net, ns2.mydnspt.net, ns7.mydnspt.net…) for cocktailteam.net from Aug 1, 2018 to Mar 20, 2021.Source: From registration records (WHOIS / RDAP archive, who.is)
Apr 20, 2021 – Feb 21, 2022Registrar: Registrar OVH, SAS (IANA 433) in the WHOIS and RDAP records held for cocktailteam.net, from Apr 20, 2021 to Feb 21, 2022.Source: WHOIS / RDAP archive (who.is)
Apr 20, 2021 – Feb 21, 2022Zone file: Registration records listed ovh.net nameservers (dns13.ovh.net, ns13.ovh.net) for cocktailteam.net from Apr 20, 2021 to Feb 21, 2022.Source: From registration records (WHOIS / RDAP archive, who.is)
Apr 20, 2021Zone file: cocktailteam.net's nameservers moved from mydnspt.net to ovh.net between Mar 20, 2021 and Apr 20, 2021. Last seen at mydnspt.net: Mar 20, 2021 (registration record). First seen at ovh.net: Apr 20, 2021 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Apr 16, 2022 – Jun 18, 2026Registrar: Registrar FastDomain Inc. (IANA 1154) in the WHOIS and RDAP records held for cocktailteam.net, from Apr 16, 2022 to Jun 18, 2026.Source: WHOIS / RDAP archive (who.is)
Apr 16, 2022Registrant: The registrant name or organization in the registration record changed; first recorded Apr 16, 2022. 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 16, 2022 – Jun 18, 2026Zone file: Registration records listed bluehost.com nameservers (ns1.bluehost.com, ns2.bluehost.com) for cocktailteam.net from Apr 16, 2022 to Jun 18, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
Apr 16, 2022Zone file: cocktailteam.net's nameservers moved from ovh.net to bluehost.com at some point between Feb 21, 2022 and Apr 16, 2022. Last seen at ovh.net: Feb 21, 2022 (registration record). First seen at bluehost.com: Apr 16, 2022 (registration record). AboutUs holds no nameserver records for the 54 days 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)
Nov 15, 2023Registrant: The registrant name or organization in the registration record changed; first recorded Nov 15, 2023. 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
Feb 24, 2026 – Nov 19, 2026Certificate: Sectigo Limited issued 1 certificate for cocktailteam.net from Feb 24, 2026, the latest valid until Feb 24, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Mar 23, 2026 – Nov 19, 2026Certificate: Let's Encrypt issued 22 certificates for cocktailteam.net from Mar 23, 2026, the latest valid until Feb 5, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Jul 18, 2026 – Aug 18, 2026AboutUs record: Authority and Safety last refreshed Aug 18, 2026.Source: AboutUs checks
Sep 20, 2026 – Oct 20, 2026Registrar: Registrar Bluehost Inc. in the registration data recorded, first on Sep 20, 2026 and most recently on Oct 20, 2026.Source: RDAP, fetched Sep 20, 2026
3 of 4 safety checks passed (Nov 19, 2026).
Registered 2004 · site is live · HTTPS valid
cocktailteam.net 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.
latest result
Domain registered Jul 21, 2004 — 22 years old.
latest result
Registrar on record: Bluehost Inc. — unchanged since AboutUs began tracking (Sep 20, 2026).
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 93 days ago); 3/3 transport and email checks available (oldest recorded about 93 days ago). This is evidence coverage, not a probability that a website is safe.
No caution flags in the available scoring observations; this is not a complete safety assessment
Site history
Dated record — historical facts always carry their date.