Biharweb.In - Info biharweb.in

biharweb.in receives about 2,586 unique visitors and 33,614 (13.00 per visitor) page views per day which should earn about $53.57/day from advertising revenue. Estimated site value is $39,103.65. According to Alexa Traffic Rank biharweb.in is ranked number 552,552 in the world and 5.7E-5% of global Internet users visit it. Site is hosted in Poland and links to network IP address 51.83.237.64. This server supports HTTPS and HTTP/2.

About - biharweb.in


Technologies used on Website

Web Servers
Nginx
Reverse Proxy
Nginx

biharweb.in Profile

Title: BiharWeb.IN :: Bhojpuri Mp3 Songs, Bolbum Mp3, Navratri Mp3, Holi Mp3 Song, Chhath Mp3, Movie Mp3, Album Mp3, Free Download
Description: Bhojpuri Mp3, Bhojpuri Holi, Bhojpuri Single, Bhojpuri Dj Remix,
Keywords: Bhojpuri Mp3, Bhojpuri Holi, Bhojpuri Single, Bhojpuri Dj Remix,.
Last update was 30 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with biharweb.in in any way. Only publicly available statistics data are displayed.

How popular is biharweb.in?

2.6K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
2,586
Monthly Unique Visitors:
62,064
Pages per Visit:
13.00
Daily Pageviews:
33,614
Alexa Rank:
552,552 visit alexa
Alexa Reach:
5.7E-5%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Users%Pageviews%Rank
India 94.1%99.6%29140

Where do visitors go on this site?

Reach%Pageviews%PerUser
biharweb.in
100.00%100.00%14

Competitive Data

SEMrush
Domain:
  biharweb.in
Rank:
(Rank based on keywords, cost and organic traffic)
  22,951,119
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  3
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is biharweb.in?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
biharweb.in
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
biharweb.in
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much biharweb.in can earn?

Daily Revenue:
$53.57
Monthly Revenue:
$1,607.10
Yearly Revenue:
$19,553.05
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
India 33,480$53.57

How much money do biharweb.in lose due to Adblock?

Daily Revenue Loss:
$15.00
Monthly Revenue Loss:
$449.97
Yearly Revenue Loss:
$5,474.58
Daily Pageviews Blocked:
9,374
Monthly Pageviews Blocked:
281,228
Yearly Pageviews Blocked:
3,421,609
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
India 9,374$15.00

How much is biharweb.in worth?

Website Value:
$39,103.65

+ Where is biharweb.in hosted?

Server IP:
51.83.237.64
ASN:
AS16276 
ISP:
OVH SAS 
Server Location:

Poland, PL
 

Other sites hosted on 51.83.237.64

+ How fast does biharweb.in load?

Average Load Time:
(789 ms) 87 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Speed Index 0.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 746 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://biharweb.in/images/BiharWeb.IN.png
733 KB
https://biharweb.in/
5 KB
https://biharweb.in/css/biharweb.css?1912
3 KB
https://biharweb.in/images/audio.jpg
1 KB
https://biharweb.in/images/new.png
1 KB
https://biharweb.in/images/artist.png
1 KB
https://biharweb.in/images/disclaimer.png
1 KB
https://biharweb.in/images/top21.png
1 KB
https://biharweb.in/images/Arrow.png
1 KB
http://biharweb.in/
0 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
48 ms
Rendering
36 ms
Other
29 ms
Parse HTML & CSS
10 ms
Script Evaluation
2 ms
Script Parsing & Compilation
1 ms
Serve images in next-gen formats - Potential savings of 489 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
https://biharweb.in/images/BiharWeb.IN.png
733 KB489 KB
Avoids an excessive DOM size - 499 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
499
Maximum DOM Depth
9
Maximum Child Elements
34
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://biharweb.in/)
0
https://biharweb.in/
190
Keep request counts low and transfer sizes small - 10 requests • 746 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
10746 KB
Image
7738 KB
Document
15 KB
Stylesheet
13 KB
Other
10 KB
Media
00 KB
Font
00 KB
Script
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 70 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://biharweb.in/css/biharweb.css?1912
3 KB70
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://biharweb.in/
0 ms152 ms0 KB0 KB302text/html
https://biharweb.in/
153 ms365 ms5 KB24 KB200text/htmlDocument
https://biharweb.in/css/biharweb.css?1912
379 ms502 ms3 KB9 KB200text/cssStylesheet
https://biharweb.in/images/BiharWeb.IN.png
379 ms1103 ms733 KB733 KB200image/pngImage
https://biharweb.in/images/audio.jpg
380 ms502 ms1 KB1 KB200image/jpegImage
https://biharweb.in/images/artist.png
382 ms862 ms1 KB1 KB200image/pngImage
https://biharweb.in/images/new.png
382 ms504 ms1 KB1 KB200image/pngImage
https://biharweb.in/images/top21.png
383 ms513 ms1 KB0 KB200image/pngImage
https://biharweb.in/images/disclaimer.png
383 ms506 ms1 KB0 KB200image/pngImage
https://biharweb.in/images/Arrow.png
513 ms635 ms1 KB0 KB200image/pngImage
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
401 ms
8 ms
412 ms
10 ms
422 ms
15 ms
541 ms
41 ms
588 ms
15 ms
1155 ms
11 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
126 ms2 ms1 ms
Properly size images - Potential savings of 729 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
https://biharweb.in/images/BiharWeb.IN.png
733 KB729 KB
Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Avoid chaining critical requests - 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 210 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

First Meaningful Paint 1.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
First Contentful Paint (3G) 2490 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 1.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.3 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://biharweb.in/)
0
https://biharweb.in/
630
Keep request counts low and transfer sizes small - 10 requests • 746 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
10746 KB
Image
7738 KB
Document
15 KB
Stylesheet
13 KB
Other
10 KB
Media
00 KB
Font
00 KB
Script
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 180 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://biharweb.in/css/biharweb.css?1912
3 KB180
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://biharweb.in/
0 ms382 ms0 KB0 KB302text/html
https://biharweb.in/
383 ms604 ms5 KB24 KB200text/htmlDocument
https://biharweb.in/css/biharweb.css?1912
615 ms738 ms3 KB9 KB200text/cssStylesheet
https://biharweb.in/images/BiharWeb.IN.png
615 ms1338 ms733 KB733 KB200image/pngImage
https://biharweb.in/images/audio.jpg
616 ms1296 ms1 KB1 KB200image/jpegImage
https://biharweb.in/images/artist.png
617 ms738 ms1 KB1 KB200image/pngImage
https://biharweb.in/images/new.png
617 ms1293 ms1 KB1 KB200image/pngImage
https://biharweb.in/images/top21.png
617 ms937 ms1 KB0 KB200image/pngImage
https://biharweb.in/images/disclaimer.png
617 ms739 ms1 KB0 KB200image/pngImage
https://biharweb.in/images/Arrow.png
744 ms866 ms1 KB0 KB200image/pngImage
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
627 ms
6 ms
635 ms
6 ms
640 ms
6 ms
761 ms
22 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
267 ms8 ms3 ms
Properly size images - Potential savings of 706 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
https://biharweb.in/images/BiharWeb.IN.png
733 KB706 KB
Avoids enormous network payloads - Total size was 746 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://biharweb.in/images/BiharWeb.IN.png
733 KB
https://biharweb.in/
5 KB
https://biharweb.in/css/biharweb.css?1912
3 KB
https://biharweb.in/images/audio.jpg
1 KB
https://biharweb.in/images/new.png
1 KB
https://biharweb.in/images/artist.png
1 KB
https://biharweb.in/images/disclaimer.png
1 KB
https://biharweb.in/images/top21.png
1 KB
https://biharweb.in/images/Arrow.png
1 KB
http://biharweb.in/
0 KB
Minimizes main-thread work - 0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
97 ms
Other
89 ms
Rendering
47 ms
Parse HTML & CSS
23 ms
Script Evaluation
8 ms
Script Parsing & Compilation
3 ms
Serve images in next-gen formats - Potential savings of 489 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
https://biharweb.in/images/BiharWeb.IN.png
733 KB489 KB
Avoids an excessive DOM size - 499 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
499
Maximum DOM Depth
9
Maximum Child Elements
34
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 220 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Avoid chaining critical requests - 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 721.3KiB (98% reduction).

Compressing and resizing https://biharweb.in/images/BiharWeb.IN.png could save 720.9KiB (98% reduction).
Compressing https://biharweb.in/images/audio.jpg could save 406B (50% reduction).

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

https://biharweb.in/css/biharweb.css?1912

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="/categorylist/…9%29/default/1">Bhojpuri Dj Songs</a> and 5 others are close to other tap targets .
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does biharweb.in use compression?

biharweb.in use gzip compression.
Original size: 24.06 KB
Compressed size: 4.27 KB
File reduced by: 19.79 KB (82%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

biharweb.in supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: biharweb.in
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Nov 20 11:25:47 2019 GMT
Valid until: Feb 18 11:25:47 2020 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

biharweb.in supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx
Date: Thu, 19 Dec 2019 08:04:22 GMT
Content-Type: text/html; charset=iso-8859-1
Content-Length: 204
Connection: keep-alive
Location: https://biharweb.in/

HTTP/2 200 
server: nginx
date: Thu, 19 Dec 2019 08:04:22 GMT
content-type: text/html; charset=utf-8
cache-control: 
expires: 
pragma: 
content-encoding: gzip
vary: Accept-Encoding
etag: "53c87c77add54d021c86133843f27e4c"

+ DNS Lookup

Type Ip Target TTL
MX biharweb.in 3600
SOA 3600
Mname f1.redserverhost.com
Rname skillvent2.gmail.com
Serial Number 2019120902
Refresh 3600
Retry 7200
Expire 1209600
Minimum TTL 0
TXT 3600
A 51.83.237.64 3573
NS f1.redserverhost.com 3572
NS f2.redserverhost.com 3572

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.inregistry.net...
\Error - could not open a connection to whois.inregistry.net
Last update was 30 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with biharweb.in in any way. Only publicly available statistics data are displayed.
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
biharweb.in widget