dizi.com — domain analysis

200HTTP status

113msResponse time

80Words on the homepage

0/6Security headers set

What is dizi.com about?

The words appearing most often on the homepage, excluding common filler, are
a rough indication of subject matter rather than a description of the business:

• dizi ×4
• series ×4
• turkish ×3
• international ×3
• home ×2
• world ×2
• channel ×2

Does dizi.com publish the usual trust pages?

Found: about. Not found at the usual addresses:
contact, privacy, terms.

These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.

How does dizi.com compare with other domains analysed here?

Measured against the 74 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.

Related domains in this index

Analysed domains sharing the same network (AS209242 Cloudflare London, LLC):

• godaddy.com

Sharing a network means sharing a host or CDN. It implies nothing about a
relationship between the sites themselves.

Analysed domains built on a similar stack:

• blabtime.com
• brandcolumn.com
• brandhivey.com
• businessofminds.com
• boll.com
• dellacooks.com
• dmfollow.com
• dugun.com

Other analysed domains served from the same country:

• ani.com
• bonistas.com
• google.com
• latam.com
• msn.com
• touro.com
• vanillagift.com

When was dizi.com registered?

dizi.com was registered on 8 May 2003, which makes it about 23 years old.

A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.

The registrar of record is GoDaddy.com, LLC.

Registration runs until 8 May 2027.

The domain carries 4 registry locks, which blocks unauthorised transfer or deletion.

Where is dizi.com hosted?

The first address resolves to infrastructure in Tempe, United States.

The network is operated by GoDaddy.com, LLC (AS209242 Cloudflare London, LLC).

Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.

What is dizi.com running on?

dizi.com exposes 5 identifiable technologies: WordPress, Bootstrap, jQuery, Google Tag Manager, Cloudflare.

WordPress is identifiable from its asset paths, so the platform is public knowledge regardless of whether the version is hidden. That matters mainly for patching discipline: known-platform sites are scanned automatically and constantly.

Cloudflare sits in front of the origin, so the server header, IP addresses and response timing describe the edge rather than the machine actually running the site.

Visitor tracking is present (Google Tag Manager), so this homepage is not cookie-free.

• WordPress
• Bootstrap
• jQuery
• Google Tag Manager
• Cloudflare

The page declares a generator of WordPress 7.0.6.

How does the homepage respond?

The server answered with HTTP 200 over
HTTPS.

At 113ms to first byte this response is fast for a homepage measured from a single European location.

The HTML weighs 70KB, which is ordinary for a homepage.

The HTML is compressed with gzip.

What does the homepage say about itself?

The title is only 11 characters, which is short enough that it probably is not describing the page so much as naming it.

A meta description of 125 characters is present.

9 of 18 images carry no alt attribute, which leaves them unreadable to screen readers and uninterpretable to image search.

Is dizi.com served over a valid certificate?

The HTTPS certificate is issued by Google Trust Services and is
valid until 2026-11-12, which is 38 days from the date of this check. It covers
2 hostnames.

• dizi.com
• *.dizi.com

The certificate has 38 days left to run.

It covers 2 hostnames, so it was issued for this site specifically.

Which security headers does it set?

None of the 6 headers checked are set. That is the default state of most servers rather than evidence of a problem, but it means the browser is given no instructions it could otherwise act on.

Without HSTS, a browser that has never visited before will try HTTP first, which is the window a network attacker needs.

With no Content Security Policy, any script that reaches the page — including one injected through a compromised third-party dependency — runs with full access to it.

How is DNS configured for dizi.com?

dizi.com resolves to a single address, so there is no DNS-level redundancy.

No MX records are published, so this domain does not receive mail at its apex. Mail sent to it will bounce.

No SPF record is published. Receiving servers therefore have no published rule for who may send mail as this domain, which makes spoofing it materially easier.

Reverse DNS resolves to 180.0.153.160.host.secureserver.net, which usually names the hosting provider.

Who runs DNS and mail for dizi.com?

DNS is operated by GoDaddy rather than self-hosted name servers.

No AAAA records are published, so the site is reachable over IPv4 only.

What else is worth noting about dizi.com?

17 of 17 externally hosted scripts carry no subresource integrity hash. If one of those hosts were compromised, the replacement script would run with full access to the page.

Can dizi.com be spoofed in email?

No DMARC record is published, so there is no instruction telling receiving servers what to do with mail that fails authentication. In practice that means forged mail from this domain is likely to be delivered.

No CAA records are published, so any certificate authority may issue a certificate for this domain.

The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.

What does robots.txt allow?

robots.txt is 24 bytes and names
1 user-agent group.

It does not blanket-disallow general crawlers.

No sitemap is declared in robots.txt.

AI crawler policy

robots.txt names no AI crawlers specifically, so they fall under whatever rule
applies to User-agent: *.

What structured data does the homepage publish?

• EntertainmentBusiness
• Organization
• WebSite
• SearchAction
• WebPage
• Person
• ImageObject
• Article
• SiteNavigationElement
• VideoObject

The homepage publishes 10 structured data types: EntertainmentBusiness, Organization, WebSite, SearchAction, WebPage, Person, ImageObject, Article, SiteNavigationElement, VideoObject.

What does dizi.com load from third parties?

The homepage pulls resources from 4 third-party hosts (fonts.googleapis.com, gmpg.org, googletagmanager.com, html5shim.googlecode.com). Each one sees the visitor IP and user agent on every page load.

1 cookie is set before any interaction (__cf_bm).

1 resource is referenced over plain HTTP on an HTTPS page, which browsers block or flag as mixed content.

The page links or refers to Facebook.

Does dizi.com settle on one address?

Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.

The www address redirects to https://dizi.com/, so the site settles on one canonical hostname.

How easily can dizi.com be crawled?

A sitemap index is served at https://dizi.com/sitemap.xml listing 5 entries.

The most recent lastmod date is 2026-07-02.

A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.

What tracking does dizi.com run?

2 tracking scripts detected: Google Tag Manager, Meta Pixel.

No consent management platform was detected alongside them. Where GDPR or the ePrivacy Directive applies, analytics and advertising scripts generally need consent before they load.

How does dizi.com look when shared?

4 of 5 social preview tags are set. Missing: og:image.

How are images, fonts and scripts handled?

18 images on the homepage, 0 of them lazy-loaded (0%).

All image references use JPEG, PNG or GIF. WebP or AVIF typically cut image weight substantially at the same visual quality.

No srcset attributes are used, so every device is served the same image size regardless of screen.

Fonts are loaded from Google Fonts, which means every page view also contacts Google. Self-hosting removes that dependency.

The page pulls 13 external stylesheets and 18 external scripts, with 0 carrying defer or async.

No preconnect hints are declared despite third-party scripts being present, so each new origin pays a full connection setup before it can deliver anything.

Responses carry Cloudflare edge headers, so content is served from a CDN rather than straight from the origin.

Is dizi.com accessible and current?

The page uses 1 landmark element and 0 ARIA attributes.

The viewport tag disables pinch-zoom. That fails WCAG 1.4.4 and is a genuine problem for anyone who needs to enlarge text.

No skip-to-content link was found, which keyboard users rely on to bypass navigation.

Can search engines index dizi.com?

Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.

The homepage carries 12 internal and 1 external link across 1 outside host.

Visible text is only 0.8% of the HTML, which indicates the page is assembled in the browser rather than served as content.

The heading outline skips 1 level, which breaks the document structure screen readers navigate by.

How is dizi.com delivered?

The HTML is served with Cache-Control: public, max-age=2678400.

HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.

Frequently asked questions

Does dizi.com set the usual HTTP security headers?

It sets 0 of 6. The ones not present are: HSTS, Content Security Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.

Does dizi.com allow AI crawlers?

robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.

What is dizi.com built with?

The homepage exposes these fingerprints: WordPress, Bootstrap, jQuery, Google Tag Manager, Cloudflare. A site behind a CDN or rendered server-side may use more than it reveals.

Where does this data come from?

Every figure was measured by our own server on 5 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.

Is any of this traffic or authority data?

No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.

I own dizi.com and want this page removed.

Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.

Analysed 5 October 2026.
Analyse another domain →