2embed.cc

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200Family DNS blockedSSL: 75 days left3 years oldTranco #242496

One re-check per domain each UTC day.

50

2embed.cc was registered on 15 Mar 2023 via NameCheap, Inc. and the registry expiry is 15 Mar 2027. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/2embed.cc.

2embed.cc publishes 2 nameservers. DNSSEC is not signed.

2embed.cc has 1 IPv4 address (45.88.138.40). The geolocation database places 45.88.138.40 in Amsterdam, The Netherlands.

The TLS certificate from YR1 is valid and has 75 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Apache HTTP Server and ShareThis. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

2embed.cc was registered on 15 Mar 2023 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/2embed.cc.

Registeredsince 15 Mar 2023
Created15 March 2023
Updated20 June 2026
Expires15 March 2027
RegistrarNameCheap, Inc.
Statusclient transfer prohibited
Nameserversns1.2embed.cc, ns2.2embed.cc
DNSSECno
Sourcehttps://tld-rdap.verisign.com/cc/v1/domain/2embed.cc

2embed.cc carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.

Nameserver ns1.2embed.cc is published for 2embed.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/2embed.cc.

Nameserver ns2.2embed.cc is published for 2embed.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/2embed.cc.

DNS

2embed.cc has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A45.88.138.40
AAAA—
NSns1.2embed.cc, ns2.2embed.cc
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 45.88.138.40 answers for 2embed.cc at resolver 1.1.1.1:53.

Hosting and geo

2embed.cc is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).

Address45.88.138.40
CountryThe Netherlands
CityAmsterdam
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for 2embed.cc is valid, with 75 days left and 2 subject alternative names. Source: tls:443.

IssuerYR1
Subject2embed.cc
Valid from16 October 2026
Valid until14 January 2027
Days left75
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: 2embed.cc, www.2embed.cc.

Tech stack

Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.

  • Apache HTTP Server · Web servers
  • ShareThis · Widgets

Apache HTTP Server is filed under Web servers.

ShareThis is filed under Widgets.

On-page checks

The homepage returned HTTP 200 in 21 ms. The target title is 48 characters and the page has 0 H1 headings.

Status200
TTFB21 ms
Title length48 yes
Quoted title"2Embed - Stream Movies, Tv-Shows, IMDB, TMDB API"
Meta description"2Embed is a movie, tv-series streaming API to stream movies by IMDB and TMDB ID. Biggest library to embed on your websites and blogs for free." yes
H1 count0
HSTSno no
CSPno
X-Frame-Options—
Robots metaindex, follow
Canonical—
Languageen
Links22
Images3
Faviconyes

The quoted title and meta description are measurements of the other site. They are not this page's title or description.

Security

Family DNS for 2embed.cc is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

Cloudflare family DNS returned a block for 2embed.cc. That resolver covers adult and malware names.

Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.

Score breakdown

Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.

TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.

DNS hygiene 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.

Safety lists 0 of 15. Points only when the checks ran and came back clean. Unknown is not clean.

Domain age 5 of 5. Five points at one year, two points at 30 days.

Change history

  • October 2026: geo city changed from empty to Amsterdam.
  • October 2026: geo country changed from empty to The Netherlands.

Questions

Is 2embed.cc safe?

Cloudflare family DNS returned a block for 2embed.cc. That resolver covers adult and malware names.

Who hosts 2embed.cc?

2embed.cc is placed in Amsterdam, The Netherlands.

When does 2embed.cc expire?

2embed.cc expires on 15 March 2027 according to https://tld-rdap.verisign.com/cc/v1/domain/2embed.cc.

Who owns 2embed.cc?

The registry did not return a person or a company for 2embed.cc. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..

Sources

  • RDAP source https://tld-rdap.verisign.com/cc/v1/domain/2embed.cc at 2026-10-30T13:33:21Z
  • DNS source 1.1.1.1:53 at 2026-10-30T13:33:21Z
  • TLS source tls:443 at 2026-10-30T13:33:21Z
  • HTTP source https://2embed.cc/ at 2026-10-30T13:33:21Z
  • Tech source wappalyzergo at 2026-10-30T13:33:21Z
  • Geo source db-ip at 2026-10-30T13:33:21Z
  • Safety source family DNS and local lists at 2026-10-30T13:33:21Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.cc NameCheap, Inc.

Owner of this site?

Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.

Removal policy

How to read this report

The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.