hotstar.com

hotstar.com is SSL secured

Free website and domain report on hotstar.com

Last Updated: 24th October, 2024 Update Now
Overview

Snoop Summary for hotstar.com

This is a free and comprehensive report about hotstar.com. Our records indicate that hotstar.com is privately registered by Privacy Protect, LLC (PrivacyProtect.org). Hotstar.com is expected to earn an estimated $181,629 USD per day from advertising revenue. The sale of hotstar.com would possibly be worth $132,589,519 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Hotstar.com receives an estimated 13,146,624 unique visitors every day - an unbelievable amount of traffic! This report was last updated 24th October, 2024.

About hotstar.com

Site Preview: hotstar.com hotstar.com
Title: Access Denied
Description: Hotstar.com
Keywords and Tags: entertainment, hindi movies online, hostar, hot star, hotstar, hotstar india, hotstar login, hotstar subscription, hotstar us, popular, streaming media, us hotstar, yeh rishta kya kehlata hai
Related Terms: hotstar mod apk, hotstar offer, hotstar watch party extension, hotstar.com, how to activate hotstar premium free, sadda haq hotstar serial, suvreen guggal hotstar serial, tere liye hotstar serial
Fav Icon:
Age: Over 28 years old
Domain Created: 16th February, 1996
Domain Updated: 26th September, 2023
Domain Expires: 26th September, 2033
Review

Snoop Score

5/5 (Perfect!)

Valuation

$132,589,519 USD
Note: All valuation figures are estimates.

Popularity

Worldwide Sensation
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 189
Alexa Reach:
SEMrush Rank (US): 3,540
SEMrush Authority Score: 64
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 197,747 3,549
Traffic: 890,240 46,378
Cost: $941,110 USD $80,370 USD
Traffic

Visitors

Daily Visitors: 13,146,624
Monthly Visitors: 400,141,821
Yearly Visitors: 4,798,517,760
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $181,629 USD
Monthly Revenue: $5,528,229 USD
Yearly Revenue: $66,294,755 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 1,154,976
Referring Domains: 10,645
Referring IPs: 13,231
Hotstar.com has 1,154,976 backlinks according to SEMrush. 93% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve hotstar.com's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of hotstar.com's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://www.motionpictures.org/watch-it-legally/
Target: https://www.hotstar.com/us

2
Source: https://www.bizasialive.com/ktv-in-trouble-with-ofcom-for-undue-prominence-in-regular-show/
Target: https://www.hotstar.com/gb

3
Source: https://www.bizasialive.com/
Target: https://www.hotstar.com/gb

4
Source: https://www.forum-course-de-cote.com/
Target: https://www.hotstar.com/us

5
Source: https://www.thelifesway.com/
Target: https://www.hotstar.com/in/tv/criminal-justice/s-2086

Top Ranking Keywords (US)

1
Keyword: hotstar
Ranked Page: https://www.hotstar.com/us

2
Keyword: hotstar us
Ranked Page: https://www.hotstar.com/us/

3
Keyword: us hotstar
Ranked Page: https://www.hotstar.com/us/

4
Keyword: hostar
Ranked Page: https://www.hotstar.com/us

5
Keyword: hotstar login
Ranked Page: https://www.hotstar.com/us/subscribe/my-account

Domain Analysis

Value Length
Domain: hotstar.com 11
Domain Name: hotstar 7
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.87 seconds
Load Time Comparison: Faster than 79% of sites

PageSpeed Insights

Avg. (All Categories) 74
Performance 86
Accessibility 52
Best Practices 69
SEO 83
PWA 78
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.hotstar.com/us
Updated: 19th February, 2022

0.87 seconds
First Contentful Paint (FCP)
89%
7%
4%

0.00 seconds
First Input Delay (FID)
99%
1%
0%

Simulate loading on desktop
86

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for hotstar.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.5 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.5 s
The time taken for the page to become fully interactive.
Speed Index — 1.2 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 40 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 130 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.5 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://hotstar.com/
http/1.1
0
58.166000002529
431
0
301
text/plain
https://www.hotstar.com/
http/1.1
58.508000016445
245.13900000602
582
0
302
text/plain
https://www.hotstar.com/us
h2
245.40800001705
583.9510000078
28732
135074
200
text/html
Document
https://www.hotstar.com/assets/main.5c52d9ba37e615303dc8.js
h2
594.29200002342
1430.3960000107
357906
1462621
200
application/javascript
Script
https://www.hotstar.com/assets/vendor~main.89.d3aff7007cc195a63938.js
h2
594.49800002039
1506.5410000097
135060
438017
200
application/javascript
Script
https://www.hotstar.com/assets/common-chunk-main.0.7e6fa7f7cb9be73453df.js
h2
594.77500000503
3985.4720000003
19576
71544
200
application/javascript
Script
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
h2
600.63200001605
726.93500001333
7855
7534
200
image/png
Image
https://secure-media.hotstar.com/static/sunset/us/assets/web/background-2.png
h2
603.19100000197
805.14900002163
1238075
1237751
200
image/png
Image
https://secure-media.hotstarext.com/web-assets/prod/roboto-regular.woff2
h2
604.50000001583
690.34000000102
11446
11016
200
font/woff2
Font
https://secure-media.hotstarext.com/web-assets/prod/roboto-medium.woff2
h2
605.75500002597
692.64500000281
11485
11056
200
font/woff2
Font
https://secure-media.hotstarext.com/web-messages/core/info/v261.json
h2
1806.6050000198
1901.6620000184
29681
140442
200
application/json
Fetch
https://api.hotstar.com/um/v3/users
h2
1931.6860000254
2167.5760000071
1039
0
403
text/html
Preflight
https://secure-media.hotstarext.com/web-messages/core/error/v52.json
h2
1909.5860000234
1936.1510000017
7662
36191
200
application/json
Fetch
https://api.hotstar.com/um/v3/users
1930.3700000164
2169.8400000168
0
0
-1
Fetch
https://www.hotstar.com/assets/sunset-page.73.33b5bec7abc8d351c048.js
h2
1942.3610000231
2206.6360000172
7342
32955
200
application/javascript
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
624.531
6.409
639.147
11.095
653.279
7.089
1528.659
42.153
1592.838
253.159
1943.902
37.042
2246.873
29.755
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Hotstar.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 7 KiB
Images can slow down the page's load time. Hotstar.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
7534
6697
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Hotstar.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Hotstar.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Hotstar.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Hotstar.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 340 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.hotstar.com/us
339.539
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Hotstar.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 7 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.hotstar.com/assets/vendor~main.89.d3aff7007cc195a63938.js
6375
https://www.hotstar.com/assets/main.5c52d9ba37e615303dc8.js
1040
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 1,813 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://secure-media.hotstar.com/static/sunset/us/assets/web/background-2.png
1238075
https://www.hotstar.com/assets/main.5c52d9ba37e615303dc8.js
357906
https://www.hotstar.com/assets/vendor~main.89.d3aff7007cc195a63938.js
135060
https://secure-media.hotstarext.com/web-messages/core/info/v261.json
29681
https://www.hotstar.com/us
28732
https://www.hotstar.com/assets/common-chunk-main.0.7e6fa7f7cb9be73453df.js
19576
https://secure-media.hotstarext.com/web-assets/prod/roboto-medium.woff2
11485
https://secure-media.hotstarext.com/web-assets/prod/roboto-regular.woff2
11446
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
7855
https://secure-media.hotstarext.com/web-messages/core/error/v52.json
7662
Avoids an excessive DOM size — 38 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
38
Maximum DOM Depth
5
Maximum Child Elements
30
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Hotstar.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures — 1 user timing
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
sentry-tracing-init
Mark
1784.872
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.hotstar.com/assets/vendor~main.89.d3aff7007cc195a63938.js
260.381
241.826
7.558
https://www.hotstar.com/assets/main.5c52d9ba37e615303dc8.js
79.492
37.367
23.259
Minimizes main-thread work — 0.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
319.553
Other
75.963
Script Parsing & Compilation
38.465
Style & Layout
18.335
Parse HTML & CSS
8.262
Rendering
4.929
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 15 requests • 1,813 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
15
1856872
Image
2
1245930
Script
4
519884
Other
6
39395
Document
1
28732
Font
2
22931
Stylesheet
0
0
Media
0
0
Third-party
4
60274
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.hotstar.com/assets/vendor~main.89.d3aff7007cc195a63938.js
1550
127
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hotstar.com on mobile screens.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Reduce unused JavaScript — Potential savings of 226 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.hotstar.com/assets/main.5c52d9ba37e615303dc8.js
357906
172021
https://www.hotstar.com/assets/vendor~main.89.d3aff7007cc195a63938.js
135060
59743
Serve images in next-gen formats — Potential savings of 1,156 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://secure-media.hotstar.com/static/sunset/us/assets/web/background-2.png
1237751
1183426.05
Avoid multiple page redirects — Potential savings of 420 ms
Redirects can cause additional delays before the page can begin loading. Hotstar.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://hotstar.com/
190
https://www.hotstar.com/
230
https://www.hotstar.com/us
0

Metrics

Largest Contentful Paint — 2.5 s
The timing of the largest text or image that is painted.

Other

Serve static assets with an efficient cache policy — 4 resources found
Hotstar.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://secure-media.hotstarext.com/web-assets/prod/roboto-regular.woff2
182000
11446
https://secure-media.hotstarext.com/web-assets/prod/roboto-medium.woff2
361000
11485
https://secure-media.hotstar.com/static/sunset/us/assets/web/background-2.png
3600000
1238075
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
3600000
7855
Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
52

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of hotstar.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Hotstar.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
69

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that hotstar.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
core-js
core-js-global@2.6.12; core-js-pure@2.6.12; core-js-pure@3.0.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

Audits

Does not use HTTPS — 3 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://hotstar.com/
Allowed
http://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
Automatically upgraded to HTTPS
http://secure-media.hotstar.com/static/sunset/us/assets/web/background-2.png
Automatically upgraded to HTTPS

Audits

Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Access to fetch at 'https://api.hotstar.com/um/v3/users' from origin 'https://www.hotstar.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.
error in guest signup :: [object Object]
Failed to load resource: net::ERR_ACCESS_DENIED
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 403 (Forbidden)
Object
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.hotstar.com/assets/main.5c52d9ba37e615303dc8.js
Issues were logged in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.
Issue type
Mixed content
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for hotstar.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hotstar.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
78

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of hotstar.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hotstar.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest has a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 76
Performance 55
Accessibility 73
Best Practices 77
SEO 93
PWA 80
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.hotstar.com/us
Updated: 19th February, 2022

1.09 seconds
First Contentful Paint (FCP)
90%
7%
3%

0.01 seconds
First Input Delay (FID)
95%
3%
2%

Simulate loading on mobile
55

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for hotstar.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 1.8 s
The time taken for the first image or text on the page to be rendered.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 1.8 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://hotstar.com/
http/1.1
0
50.011000130326
416
0
301
text/plain
https://www.hotstar.com/
http/1.1
50.301000010222
133.9020000305
580
0
302
text/plain
https://www.hotstar.com/us
h2
134.35800001025
530.65000008792
28715
135044
200
text/html
Document
https://www.hotstar.com/assets/main.1110f77473b72fb7e9a6.js
h2
546.15000006743
818.45600018278
357907
1462621
200
application/javascript
Script
https://www.hotstar.com/assets/vendor~main.89.d3aff7007cc195a63938.js
h2
546.87399999239
787.63500018977
135060
438017
200
application/javascript
Script
https://www.hotstar.com/assets/common-chunk-main.0.7e6fa7f7cb9be73453df.js
h2
546.9780000858
876.39000010677
19576
71544
200
application/javascript
Script
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
h2
550.58300006203
839.1690000426
7855
7534
200
image/png
Image
https://secure-media.hotstar.com/static/sunset/us/assets/web/background-2.png
h2
553.34100010805
1195.7940000575
1238075
1237751
200
image/png
Image
https://secure-media.hotstarext.com/web-assets/prod/roboto-medium.woff2
h2
554.79199998081
703.23400013149
11485
11056
200
font/woff2
Font
https://secure-media.hotstarext.com/web-assets/prod/roboto-regular.woff2
h2
555.81300007179
841.96700016037
11446
11016
200
font/woff2
Font
https://secure-media.hotstarext.com/web-messages/core/info/v261.json
h2
1206.9520000368
1399.9080001377
29681
140442
200
application/json
Fetch
https://api.hotstar.com/um/v3/users
h2
1433.2960001193
1769.4580000825
1039
0
403
text/html
Preflight
https://secure-media.hotstarext.com/web-messages/core/error/v52.json
h2
1408.0190001987
1440.137000056
7662
36191
200
application/json
Fetch
https://api.hotstar.com/um/v3/users
1432.1840000339
1801.8770001363
0
0
-1
Fetch
https://www.hotstar.com/assets/sunset-page.73.33b5bec7abc8d351c048.js
h2
1444.2700000945
1765.4210000765
7342
32955
200
application/javascript
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
589.93
8.995
607.485
11.787
621.746
8.066
928.311
336.183
1460.896
40.316
1823.956
29.127
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Hotstar.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Hotstar.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Hotstar.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Hotstar.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Hotstar.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Hotstar.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 400 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.hotstar.com/us
397.285
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Hotstar.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 1,813 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://secure-media.hotstar.com/static/sunset/us/assets/web/background-2.png
1238075
https://www.hotstar.com/assets/main.1110f77473b72fb7e9a6.js
357907
https://www.hotstar.com/assets/vendor~main.89.d3aff7007cc195a63938.js
135060
https://secure-media.hotstarext.com/web-messages/core/info/v261.json
29681
https://www.hotstar.com/us
28715
https://www.hotstar.com/assets/common-chunk-main.0.7e6fa7f7cb9be73453df.js
19576
https://secure-media.hotstarext.com/web-assets/prod/roboto-medium.woff2
11485
https://secure-media.hotstarext.com/web-assets/prod/roboto-regular.woff2
11446
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
7855
https://secure-media.hotstarext.com/web-messages/core/error/v52.json
7662
Avoids an excessive DOM size — 15 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
15
Maximum DOM Depth
5
Maximum Child Elements
8
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Hotstar.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures — 1 user timing
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
sentry-tracing-init
Mark
1183.135
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 15 requests • 1,813 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
15
1856839
Image
2
1245930
Script
4
519885
Other
6
39378
Document
1
28715
Font
2
22931
Stylesheet
0
0
Media
0
0
Third-party
4
60274
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 3 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.hotstar.com/assets/main.1110f77473b72fb7e9a6.js
7500
672
https://www.hotstar.com/assets/main.1110f77473b72fb7e9a6.js
8172
161
https://www.hotstar.com/assets/sunset-page.73.33b5bec7abc8d351c048.js
8663
117
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hotstar.com on mobile screens.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Speed Index — 5.2 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 400 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

Avoid serving legacy JavaScript to modern browsers — Potential savings of 7 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.hotstar.com/assets/vendor~main.89.d3aff7007cc195a63938.js
6375
https://www.hotstar.com/assets/main.1110f77473b72fb7e9a6.js
1040
Reduce JavaScript execution time — 1.6 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.hotstar.com/assets/vendor~main.89.d3aff7007cc195a63938.js
1161.548
1104.252
33.98
https://www.hotstar.com/assets/main.1110f77473b72fb7e9a6.js
367.488
163.532
110.696
https://www.hotstar.com/us
232.856
17.632
27.292
Unattributable
169.416
28.912
0.444
https://www.hotstar.com/assets/sunset-page.73.33b5bec7abc8d351c048.js
117.78
113.02
2.24
Minimize main-thread work — 2.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1428.332
Other
300.448
Script Parsing & Compilation
179.968
Style & Layout
66.72
Parse HTML & CSS
54.012
Rendering
25.636
Garbage Collection
4.904
First Contentful Paint (3G) — 3414 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

Time to Interactive — 7.4 s
The time taken for the page to become fully interactive.
Largest Contentful Paint — 12.6 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 670 ms
Users could experience a delay when interacting with the page.

Other

Reduce unused JavaScript — Potential savings of 228 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.hotstar.com/assets/main.1110f77473b72fb7e9a6.js
357907
172693
https://www.hotstar.com/assets/vendor~main.89.d3aff7007cc195a63938.js
135060
60706
Serve images in next-gen formats — Potential savings of 1,156 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://secure-media.hotstar.com/static/sunset/us/assets/web/background-2.png
1237751
1183426.05
Avoid multiple page redirects — Potential savings of 1,410 ms
Redirects can cause additional delays before the page can begin loading. Hotstar.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://hotstar.com/
630
https://www.hotstar.com/
780
https://www.hotstar.com/us
0
Serve static assets with an efficient cache policy — 4 resources found
Hotstar.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://secure-media.hotstarext.com/web-assets/prod/roboto-regular.woff2
255000
11446
https://secure-media.hotstarext.com/web-assets/prod/roboto-medium.woff2
341000
11485
https://secure-media.hotstar.com/static/sunset/us/assets/web/background-2.png
3600000
1238075
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
3600000
7855
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
73

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of hotstar.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Hotstar.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
77

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that hotstar.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
core-js
core-js-global@2.6.12; core-js-pure@2.6.12
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

Audits

Does not use HTTPS — 3 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://hotstar.com/
Allowed
http://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
Automatically upgraded to HTTPS
http://secure-media.hotstar.com/static/sunset/us/assets/web/background-2.png
Automatically upgraded to HTTPS

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Access to fetch at 'https://api.hotstar.com/um/v3/users' from origin 'https://www.hotstar.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.
error in guest signup :: [object Object]
Failed to load resource: net::ERR_FAILED
Object
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.hotstar.com/assets/main.1110f77473b72fb7e9a6.js
Issues were logged in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.
Issue type
Mixed content
93

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for hotstar.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hotstar.com on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
80

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of hotstar.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hotstar.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest has a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 18.238.55.86
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Amazon.com, Inc.
Registration

Domain Registrant

Private Registration: Yes
Name: Domain Admin
Organization: Privacy Protect, LLC (PrivacyProtect.org)
Country: US
City: Burlington
State: MA
Post Code: 01803
Email: contact@privacyprotect.org
Phone: +1.8022274003
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
CSC CORPORATE DOMAINS, INC. 204.74.99.103
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 87/100
WOT Child Safety: 88/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: www.hotstar.com
Issued By: DigiCert TLS RSA SHA256 2020 CA1
Valid From: 1st October, 2024
Valid To: 16th September, 2025
Subject: CN = www.hotstar.com
O = Novi Digital Entertainment Pvt. Ltd.
L = Mumbai
S = IN
Hash: b7af2564
Issuer: CN = DigiCert TLS RSA SHA256 2020 CA1
O = DigiCert Inc
S = US
Version: 2
Serial Number: 13379845337322625038137769667133149296
Serial Number (Hex): 0A10DD4E78E74CD86F4A906CCDC39070
Valid From: 1st October, 2024
Valid To: 16th September, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:B7:6B:A2:EA:A8:AA:84:8C:79:EA:B4:DA:0F:98:B2:C5:95:76:B9:F4
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl

Full Name:
URI:http://crl4.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/DigiCertTLSRSASHA2562020CA1-1.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
Timestamp : Oct 1 08:37:31.250 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:0B:EA:D8:FF:B6:83:53:CC:F2:85:89:49:
6D:DB:29:D3:30:9F:DD:91:8D:02:42:8A:BA:07:85:80:
D6:AC:5F:A7:02:20:16:75:C2:91:35:09:B0:4C:BD:AC:
B3:70:B7:C0:95:11:67:74:BE:32:7A:FA:B3:88:99:CA:
73:F9:D2:9D:93:6F
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
Timestamp : Oct 1 08:37:31.122 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:89:66:79:83:4C:7F:8F:7D:61:AC:35:
79:2F:D5:41:74:49:BD:BD:DC:34:23:9B:92:34:D2:CF:
AC:D0:24:0D:14:02:20:2E:F2:74:A3:8F:74:A7:B3:D7:
A2:D8:FB:D3:1A:D8:11:7B:B0:6A:BB:B9:71:85:6A:F8:
4D:56:6F:69:99:06:52
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
Timestamp : Oct 1 08:37:31.245 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:3D:01:CD:E2:0E:EE:A8:A4:7A:67:22:F6:
89:54:93:E9:58:FC:8B:74:E4:A3:84:B2:EC:E1:AD:CF:
69:01:A3:11:02:20:37:93:0F:64:1C:D9:32:BF:5B:E4:
91:CC:91:F9:33:6C:04:E0:2C:80:F9:C1:B2:F9:28:03:
B2:FD:7B:E4:87:55
Key Usage: Digital Signature, Key Agreement
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:apix.hotstar.com
DNS:bifrost-api.hotstar.com
DNS:hf-apix.hotstar.com
DNS:service.hotstar.com
DNS:web.hotstar.com
DNS:www.hotstar.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
hotstar.com. 3.162.174.69 IN 60
hotstar.com. 3.162.174.60 IN 60
hotstar.com. 3.162.174.65 IN 60
hotstar.com. 3.162.174.103 IN 60

NS Records

Host Nameserver Class TTL
hotstar.com. ns-753.awsdns-30.net. IN 3600
hotstar.com. ns-1645.awsdns-13.co.uk. IN 3600
hotstar.com. ns-1296.awsdns-34.org. IN 3600
hotstar.com. ns-484.awsdns-60.com. IN 3600

MX Records

Priority Host Server Class TTL
5 hotstar.com. mxa-0083d201.gslb.pphosted.com. IN 60
5 hotstar.com. mxb-0083d201.gslb.pphosted.com. IN 60

SOA Records

Domain Name Primary NS Responsible Email TTL
hotstar.com. ns-753.awsdns-30.net. awsdns-hostmaster.amazon.com. 900

TXT Records

Host Value Class TTL
hotstar.com. lm7hmk8gvch9kksr31sg2958080sdh2v IN 30
hotstar.com. adobe-idp-site-verification=012b7d24aff9766444b9232173abb52ef026139e50aac77c49e02bd5d0dc3916 IN 30
hotstar.com. scnv-verification=ef6859457ccd3826e10ba10ec65d175c:01b32a0ce62ea4595d6861d6da9b9a2c:498da58ba3634642b0f41cd533f11fee IN 30
hotstar.com. MS=ms38797924 IN 30
hotstar.com. ltcgnb1gwyjb5rhqppxqlbwkgq8fpvct IN 30
hotstar.com. v=spf1 IN 30
hotstar.com. google-site-verification=4RCh10k-Kyhb1QcVRnWgNTL7wxb7RmlExDI2EUhxnpA IN 30
hotstar.com. n8f6bdf26r5y8m18wty625rsl2r88rrx IN 30
hotstar.com. tw8dt0txxkr3kpx59y2b8mwk2dc8045n IN 30
hotstar.com. facebook-domain-verification=wekg44k3fcbx3ivc3r8ytshbv1uh22 IN 30
hotstar.com. xtdhwlyv8724g2gcr8xpztr32tzn608f IN 30
hotstar.com. google-site-verification=oVwi7WWGjloUhkLF9uFeNftW3FwN63LF3o94WjuczaU IN 30
hotstar.com. dzz6bn9lgbxgzhd3qskcchn22kxk5m2p IN 30
hotstar.com. 5f3mq9t2qhglvkwthvv587lyq23trtdj IN 30
hotstar.com. _qe0hud3teupjdxni8oxunahlb72oc1u IN 30
hotstar.com. j7xxb30bmss7yhlxmjtny3xsm70zttz9 IN 30
hotstar.com. amazonses:7Fs8k8Y3jJOBKxYA9PXKzH4+w2qSwBXN6r+WWe/cgt4= IN 30
hotstar.com. _globalsign-domain-verification=5WheSlX5FtHbapKuKfA_RaBxj3Bk0f_A-hFr-97RCf IN 30
hotstar.com. google-site-verification=tPvq2_qVNWBELm-PKE_kzdsiPGXQUG7V95Lsn6F_l1o IN 30
hotstar.com. smartsheet-site-validation=NuLxIcWcA2RGR8u1KwlW05Fun5pVwiXo IN 30
hotstar.com. box-domain-verification=3ef9f7daff7e083496430a2c38a6adf88e0e616666f8fbee57bd4078ccf8264f IN 30
hotstar.com. 2frrzdkn134zy5w2kq5nxj0rxrmr4h3t IN 30
hotstar.com. google-site-verification=6AQk4uvNpaJqHnMQsXj2VOxCyqCb49mYuHEVmsUIn3U IN 30
hotstar.com. google-site-verification=1aUIQK9Cct6c-TOF2K5gay-mhBc_1mlu6oJ_c84QDEo IN 30
hotstar.com. 58j3yl4gdmslrqt7wdgmn17db6stt33w IN 30
hotstar.com. bct08p0f32lv0dm0ww85z2wdyyfh5ff1 IN 30
hotstar.com. 14qx3dxdz5cfcn5jzcpxp7yj3d93hqgs IN 30
hotstar.com. 8wwcj072cm2lvwnqkhc8342j1pxv85h4 IN 30
hotstar.com. zy6g0332pr52n4v3nyvmdw2b8fkyvyjs IN 30
hotstar.com. k8b37k0elqktsjl35sjflsvvq2 IN 30
hotstar.com. apple-domain-verification=aX4DVISKlI2pLIjT IN 30
hotstar.com. atlassian-domain-verification=WxzzBCOAFNcN9v7zwVnCk3eo7wkU7RPsrIVinYWvcpRD89xRaYndynK3FWugyYbX IN 30
hotstar.com. 4w1qmsxlrqp6rky39l6f5pjpvb9dqhf0 IN 30
hotstar.com. _vwzit9271fhs9e5r0a5rksjl9wecdca IN 30
hotstar.com. dh22r7l8snlt98ysltnyyg2vtmj67x71 IN 30
hotstar.com. google-site-verification=bHcneppd4587MVk4HNyzhKHB7LFIfmAhv9ZBQVEpmZI IN 30

HTTP Response Headers

HTTP-Code: HTTP/2 475
server: AkamaiGHost
content-type: text/html
expires: 24th October, 2024
cache-control: max-age=0, no-cache, no-store
date: 24th October, 2024
mime-version: 1.0
content-length: 372
pragma: no-cache
set-cookie: *
alt-svc: h3=":443"; ma=93600
strict-transport-security: max-age=31536000
x-cachestatus:
x-cachettl: -1
x-origin-date: 1729793155
x-asnno: 213230
x-frame-options: SAMEORIGIN
akamai-grn: 0.adce4917.1729793155.76a3984

Whois Lookup

Created: 16th February, 1996
Changed: 26th September, 2023
Expires: 26th September, 2033
Registrar: CSC CORPORATE DOMAINS, INC.
Status: clientTransferProhibited
Nameservers: ns-1296.awsdns-34.org
ns-1645.awsdns-13.co.uk
ns-484.awsdns-60.com
ns-753.awsdns-30.net
Owner Name: Star India Private Limited; Domain Administrator
Owner Organization: Star India Private Limited
Owner Street: Star House, Urmi Estate, 95 Ganpatrao K Lower Parel (W) NA
Owner Post Code: 400013
Owner City: Mumbai
Owner State: MH
Owner Country: IN
Owner Phone: +1.8182384694
Owner Email: Corp.DNS.Domains@disney.com
Admin Name: Star India Private Limited; Domain Administrator
Admin Organization: Star India Private Limited
Admin Street: Star House, Urmi Estate, 95 Ganpatrao K Lower Parel (W) NA
Admin Post Code: 400013
Admin City: Mumbai
Admin State: MH
Admin Country: IN
Admin Phone: +1.8182384694
Admin Email: Corp.DNS.Domains@disney.com
Tech Name: Star India Private Limited; Domain Administrator
Tech Organization: Star India Private Limited
Tech Street: Star House, Urmi Estate, 95 Ganpatrao K Lower Parel (W) NA
Tech Post Code: 400013
Tech City: Mumbai
Tech State: MH
Tech Country: IN
Tech Phone: +1.8182384694
Tech Email: Corp.DNS.Domains@disney.com
Full Whois:
Domain Name: hotstar.com
Registry Domain ID: 1118578_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.corporatedomains.com
Registrar URL: www.cscprotectsbrands.com
Updated Date: 2023-09-26T00:16:18Z
Creation Date: 1996-02-16T00:00:00Z
Registrar Registration Expiration Date: 2033-09-26T04:15:44Z
Registrar: CSC CORPORATE DOMAINS, INC.
Sponsoring Registrar IANA ID: 299
Registrar Abuse Contact Email: domainabuse@cscglobal.com
Registrar Abuse Contact Phone: +1.8887802723
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: Star India Private Limited; Domain Administrator
Registrant Organization: Star India Private Limited
Registrant Street: Star House, Urmi Estate, 95 Ganpatrao K Lower Parel (W) NA
Registrant City: Mumbai
Registrant State/Province: MH
Registrant Postal Code: 400013
Registrant Country: IN
Registrant Phone: +1.8182384694
Registrant Phone Ext:
Registrant Fax: +1.8182384694
Registrant Fax Ext:
Registrant Email: Corp.DNS.Domains@disney.com
Registry Admin ID:
Admin Name: Star India Private Limited; Domain Administrator
Admin Organization: Star India Private Limited
Admin Street: Star House, Urmi Estate, 95 Ganpatrao K Lower Parel (W) NA
Admin City: Mumbai
Admin State/Province: MH
Admin Postal Code: 400013
Admin Country: IN
Admin Phone: +1.8182384694
Admin Phone Ext:
Admin Fax: +1.8182384694
Admin Fax Ext:
Admin Email: Corp.DNS.Domains@disney.com
Registry Tech ID:
Tech Name: Star India Private Limited; Domain Administrator
Tech Organization: Star India Private Limited
Tech Street: Star House, Urmi Estate, 95 Ganpatrao K Lower Parel (W) NA
Tech City: Mumbai
Tech State/Province: MH
Tech Postal Code: 400013
Tech Country: IN
Tech Phone: +1.8182384694
Tech Phone Ext:
Tech Fax: +1.8182384694
Tech Fax Ext:
Tech Email: Corp.DNS.Domains@disney.com
Name Server: ns-1296.awsdns-34.org
Name Server: ns-1645.awsdns-13.co.uk
Name Server: ns-753.awsdns-30.net
Name Server: ns-484.awsdns-60.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-09-26T00:16:18Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Corporation Service Company(c) (CSC) The Trusted Partner of More than 50% of the 100 Best Global Brands.

Contact us to learn more about our enterprise solutions for Global Domain Name Registration and Management, Trademark Research and Watching, Brand, Logo and Auction Monitoring, as well SSL Certificate Services and DNS Hosting.

NOTICE: You are not authorized to access or query our WHOIS database through the use of high-volume, automated, electronic processes or for the purpose or purposes of using the data in any manner that violates these terms of use. The Data in the CSC WHOIS database is provided by CSC for information purposes only, and to assist persons in obtaining information about or related to a domain name registration record. CSC does not guarantee its accuracy. By submitting a WHOIS query, you agree to abide by the following terms of use: you agree that you may use this Data only for lawful purposes and that under no circumstances will you use this Data to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, e-mail, telephone, or facsimile; or (2) enable high volume, automated, electronic processes that apply to CSC (or its computer systems). CSC reserves the right to terminate your access to the WHOIS database in its sole discretion for any violations by you of these terms of use. CSC reserves the right to modify these terms at any time.

Register your domain name at http://www.cscglobal.com

Nameservers

Name IP Address
ns-1296.awsdns-34.org 205.251.197.16
ns-1645.awsdns-13.co.uk 205.251.198.109
ns-484.awsdns-60.com 205.251.193.228
ns-753.awsdns-30.net 205.251.194.241
Related

Similar Sites

Domain Valuation Snoop Score
$923 USD 1/5
0/5
0/5
0/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5

Sites hosted on the same IP address