huggingface.co Lookup

Status
Active
Expires
2027-07-17
Expires in 238 days
Registered
2016-07-18
Domain age
10 years

huggingface.co is registered through OVH sas, and its current term runs until 17 July 2027. No one else can register it unless it lapses.

Checked 21 November 2026 over RDAP
Ownership

Who owns huggingface.co?

huggingface.co is registered through OVH sas and owned by Hugging Face, according to published sources. The public record does not name the registrant.

huggingface.co is the home of Hugging Face, the platform for sharing machine learning models and datasets.

The record was created on 18 July 2016 and last updated on 6 July 2026.

Registrar
OVH sas
Created
2016-07-18
Last updated
2026-07-06
Registry expiry
2027-07-17
DNSSEC
Signed
Show 2 status codes
  • clientTransferProhibited

    An EPP status that blocks the domain from being transferred to another registrar. It is a lock, not a problem, and most registrars set it by default. clientTransferProhibited

  • clientDeleteProhibited

    The remaining EPP prohibitions: clientUpdateProhibited and clientDeleteProhibited set by your registrar, serverUpdateProhibited and serverDeleteProhibited set by the registry, and the bundled registry lock services that apply several at once. Domain lock (update, delete and registry lock)

Sources: wikidata.org

Monitor a domain's registration and status

Unchanged since 18 November 2026.

Expiry

When does huggingface.co expire?

huggingface.co's current registration runs until 17 July 2027. Expires in 238 days.

The owner can renew at any time before then, which moves the date forward by the renewal term. Large brands usually renew years ahead.

  1. Registered
  2. Grace period 45 days
  3. Redemption 30 days
  4. Pending delete 5 days
  5. Released

What happens if it isn't renewed?

An unrenewed .co name passes through fixed phases before it is released: a 45-day grace period in which the owner can still renew at the normal price, a 30-day redemption period in which recovery costs a fee on top of renewal, then 5 days pending delete, when no one can renew or register it. The durations are the .co registry's published figures.

When could it drop?

Only if it is not renewed. The earliest it could be released is 5 October 2027, if every phase runs its full length.

How the .co lifecycle works Check huggingface.co's expiry date live Domain expiration monitoring

Availability

Is huggingface.co available to register?

No. huggingface.co is registered, so a registration attempt today would fail.

It only becomes available if the owner lets it lapse and it clears every phase above. Domain Watch checks the name twice a day and sends one email the day it is released.

Age

How old is huggingface.co?

huggingface.co is 10 years old: it was first registered on 18 July 2016.

The creation date is when the current registration began. A name that dropped and was re-registered gets a new creation date, so this counts continuous registration, not first use.

Milestones

2016
Hugging Face is founded in New York as a chatbot app company.

Sources: en.wikipedia.org

Check any domain's age

DNS

What are huggingface.co's DNS records?

huggingface.co is served by 4 nameservers and publishes 2 address records and 5 MX records.

Its nameservers are classed as Managed DNS.

Nameservers
ns-137.awsdns-17.com ns-1452.awsdns-53.org ns-1955.awsdns-52.co.uk ns-919.awsdns-50.net
A
18.165.122.101, 18.165.122.11, 18.165.122.120, 18.165.122.30
AAAA
2600:9000:2375:1e00:17:b174:6d00:93a1, 2600:9000:2375:5800:17:b174:6d00:93a1, 2600:9000:2375:6200:17:b174:6d00:93a1, 2600:9000:2375:6400:17:b174:6d00:93a1, 2600:9000:2375:8000:17:b174:6d00:93a1, 2600:9000:2375:8e00:17:b174:6d00:93a1, 2600:9000:2375:c00:17:b174:6d00:93a1, 2600:9000:2375:e400:17:b174:6d00:93a1
MX
1 aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com
SPF
v=spf1 include:spf.mailjet.com include:_spf.google.com include:amazonses.com include:mail.zendesk.com ~all
DMARC
v=DMARC1; p=none; sp=none;rua=mailto:dmarc@huggingface.co; pct=100; adkim=r; aspf=s
Show 20 TXT records
  • MS=ms73710064
  • apple-domain-verification=ZDO4wVjVjWMGBFP3
  • google-site-verification=0xPvU1qdox33LAduAR6WZBcojgN2dTHbmD6V7xH86ao
  • google-site-verification=ZlzPJH9K6WW65-qtY2MAVZedKyBrjS2hX6B6Y6mlvxQ
  • google-site-verification=lyRnnTlQ38GAC7D92RqswXMuRY6G0pRaPMyfKtNK5zw
  • miro-verification=ffff67f600b7fa1bc0e2cfeb85506a9854d04b3f
  • mongodb-site-verification=pJyVDE1qFtWfLWussktn17TxGmMiOSrO
  • openai-domain-verification=dv-e4Lrj3WKW6Ij50099jy0UDHH
  • stripe-verification=EB5A6D7C5DB936DB61416A17258106A0BE35C774B2E9532B040C5D5F6859CBF7
  • 1|www.huggingface.co
  • amazon-business-verification=edce90d350ae97c05d07c252817db08ffe470096ef197b689abfe8e5c692031d
  • amazonses:haWTX74o8Xzj4/OOGCiZvCKU2CreCZ9D+2OemeBCWW0=
  • anthropic-domain-verification-be2qx2=5duhSVDfBdfL9zp9HMwMo5DeF
  • cursor-domain-verification-e2jjpz=VS6jJT0Yi3HOWOAjVnPRBRn4R
  • hcp-domain-verification=b90e13b0828283c307c52de32fe6661bcd4da664d5486f0b552f4593ebb20505
  • plausible-sso-verification=71baae3e-8875-4d97-b492-3d0bcc09ab35
  • seatsurfing-verification=c972dd30-8319-4f60-b684-089c02e1e7bd
  • uber-domain-verification=a96220f2-0f5b-4858-b6ce-1525a1e5b3a5
  • v=MCPv1; k=ed25519; p=EWH4AejXSbTWok3hjfTSRcFXFG/Qe+oQffs4nM/Hl7k=
  • zapier-domain-verification-challenge=83bd16a2-804b-4046-8607-d0aed15cc172

Get alerts when DNS records change

Unchanged since 21 November 2026.

SSL

Does huggingface.co have a valid SSL certificate?

Yes. huggingface.co serves a certificate issued by Amazon RSA 2048 M01, valid until 27 February 2027.

Secure
Issuer
Amazon RSA 2048 M01
Valid from
2026-08-14
Valid until
2027-02-27

Monitor SSL certificate expiry

Unchanged since 18 November 2026.

Uptime

Is huggingface.co down right now?

This record covers huggingface.co's registration, DNS and certificate, read once a day. It does not test whether the website is responding right now.

On 21 November 2026 its nameservers answered. Its certificate validated on 21 November 2026.

A name that is registered, answers DNS and serves a valid certificate but still will not load has a hosting or server problem, not a registration one.

Monitoring

Monitor your own domains the same way: expiry, status, DNS and SSL, with an alert the day any of them changes.

Start monitoring