whitehouse.gov Whitehouse.gov

   
The White House

Domain Summary

What is the traffic rank for Whitehouse.gov?

• Whitehouse.gov ranks #39,045 globally on HypeStat.

What percent of global Internet users visit Whitehouse.gov?

0.0048617% of global Internet users visit Whitehouse.gov

How many people visit Whitehouse.gov each day?

• Whitehouse.gov receives approximately 239.7K visitors and 458,158 page impressions per day.

Which countries does Whitehouse.gov receive most of its visitors from?

• Whitehouse.gov is mostly visited by people located in United States,United Kingdom,Canada.

How much Whitehouse.gov can earn?

• Whitehouse.gov should earn about $2,096.06/day from advertising revenue.

What is Whitehouse.gov estimated value?

• Estimated value of Whitehouse.gov is $2,024,082.21.

What IP addresses does Whitehouse.gov resolve to?

• Whitehouse.gov resolves to the IP addresses 2a04:fa87:fffd::c000:42a8, 192.0.66.168.

Where are Whitehouse.gov servers located in?

• Whitehouse.gov has servers located in San Francisco, California, 94110, United States.

whitehouse.gov Profile

Title:The White House
Description:President Biden and Vice President Harris promised to move quickly to deliver results for working families. That’s what they’ve done.
Tags:
Category:Law and Government / Government
About: Official White House site presents issue positions, news, Cabinet, appointments, offices and major speeches. Includes biography, video tour and photo essays.
See the President's daily schedule, explore behind-the-scenes photos from inside the White House, and find out all the ways you can engage with the most interactive administration in our country's history. Edit Site Info

What technologies does whitehouse.gov use?

These are the technologies used at whitehouse.gov. whitehouse.gov has a total of 7 technologies installed in 10 different categories.

whitehouse.gov Traffic Analysis

Whitehouse.gov is ranked #39,045 in the world. This website is viewed by an estimated 239.7K visitors daily, generating a total of 458.2K pageviews. This equates to about 7.3M monthly visitors. Whitehouse.gov traffic has decreased by 12.35% compared to last month.
Daily Visitors239.7K
9.78%
Monthly Visits7.3M
12.35%
Pages per Visit1.91
0.87%
Visit duration01:24
1.27%
Bounce Rate71.07%
1.47%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
239,676
Monthly Visits:
7,262,183
Pages per Visit:
1.91
Daily Pageviews:
458,158
Avg. visit duration:
01:24
Bounce rate:
71.07%
Global Reach:
0.0048617%
Monthly Visits (SEMrush):
6,445,327
Monthly Unique Visitors (SEMrush):
5,155,616
Monthly Visits (SimilarWeb):
7,119,098
HypeRank:
39,045
SEMrush Rank:
328
SimilarWeb Rank:
11,601
*All traffic values are estimates only.

Traffic sources

Direct:
30.97%
Referral:
9.18%
Search:
54.00%
Social:
5.85%
Paid:
0%

Desktop vs Mobile

Desktop:
49.75%
Mobile:
50.25%

Total Visits Last 3 Months

7.7M
FEB
8.3M
MAR
7.3M
APR

Visitors by country

Country
Users%
 
United States 77.32%
 
United Kingdom 1.69%
 
Canada 1.68%
 
Brazil 1.48%
 
India 1.45%

Where do visitors go on whitehouse.gov?

 
Reach%Pageviews%PerUser
whitehouse.gov
99.75%99.36%1.7
events.whitehouse.gov
0.35%0.24%1
apply.whitehouse.gov
0.20%0.40%3
Last update was 318 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with whitehouse.gov in any way. Only publicly available statistics data are displayed.

Search Engine Indexes

Search engine indexes are huge databases or collections of net pages that search engines like google like google and yahoo use to retrieve applicable facts while customers carry out searches. These indexes are created through search engines like google and yahoo through crawling and indexing net pages from throughout the internet.
Google Index:
68,100
Bing Index:
85,000
Baidu Index:
96,200

 

SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.
SemRushSemRush
Domain:
  whitehouse.gov
Rank:
(Rank based on keywords, cost and organic traffic)
  328
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  1,751,068
Organic Traffic:
(Number of visitors coming from top 20 search results)
  8,367,375
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $5,918,555.00

Revenue report

Google.com would generate approximately $2.1K per day if the source of income were advertisements, which equates to an estimated monthly revenue of $62.9K and annual gross revenue of approximately $765.1K. Based on these figures, the site's net worth is estimated at around $2M.

How much would whitehouse.gov make?

Daily Revenue:
$2,096.06
Monthly Revenue:
$62,881.80
Yearly Revenue:
$765,061.90
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 354,237$1,710.96
 
Canada 7,703$46.53
 
United Kingdom 7,724$20.70
 
Brazil 6,777$9.01
 
India 6,636$2.52

Loss of money due to Adblock?

Daily Revenue Loss:
$324.16
Monthly Revenue Loss:
$9,724.94
Yearly Revenue Loss:
$118,320.05
Daily Pageviews Blocked:
69,189
Monthly Pageviews Blocked:
2,075,673
Yearly Pageviews Blocked:
25,254,023

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 63,763$307.97
 
Canada 1,926$11.63
 
United Kingdom 1,236$3.31
 
India 1,858$0.71
 
Brazil 407$0.54

How much is whitehouse.gov worth?

Website Value:
$2M

Ad Experience Report

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

Mobile summary

Root domain:
whitehouse.gov
Last Change Time:
(The last time that the site changed status.)
2018-03-06 16:06:48
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.)
Passing

Desktop summary

Root domain:
whitehouse.gov
Last Change Time:
(The last time that the site changed status.)
2018-03-06 16:06:48
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.)
Passing

Abusive Experience Report

Summary of the abusive experience rating of a website.
Root domain:
whitehouse.gov
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.)
Passing

Where is whitehouse.gov hosted?

Whitehouse.gov may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
2a04:fa87:fffd::c000:42a8, 192.0.66.168
ASN:
AS2635 
ISP:
Automattic, Inc 
Server Location:
San Francisco
California, CA
94110
United States, US
 

Other sites hosted on 192.0.66.168

How fast does whitehouse.gov load?

The average loading time of whitehouse.gov is 150 ms. The Desktop speed index is 89 and mobile speed index is 61.
Average Load Time:
150 ms

Page Speed (Google PageSpeed Insights) - Desktop

89
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE 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.

First Contentful Paint (FCP)2.7s 61% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 61% 20% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 20% 17% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 17%
First Input Delay (FID)3ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an AVERAGE 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.

First Contentful Paint (FCP)1.9s 71% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 71% 22% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 22% 6% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 6%
First Input Delay (FID)4ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

Largest Contentful Paint 1.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Has a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
Largest Contentful Paint element  
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Time to Interactive 1.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Speed Index 1.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Preconnect to required origins  
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
First Meaningful Paint 1.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more about performance budgets
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
Max Potential First Input Delay 70 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric

Page Speed (Google PageSpeed Insights) - Mobile

61
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE 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.

First Contentful Paint (FCP)2.4s 61% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 68% 14% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 14% 17% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 17%
First Input Delay (FID)14ms 94% of loads for this page have a fast (<100ms) First Input Delay (FID) 94% 4% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 4% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%

Origin Data

All pages served from this origin have an FAST 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.

First Contentful Paint (FCP)1.8s 75% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 75% 13% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 13% 11% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 11%
First Input Delay (FID)14ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 94% 4% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 4% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%

Lab Data

Total Blocking Time 70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Has a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
Speed Index 5.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
Largest Contentful Paint 8.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
First Meaningful Paint 5.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more about performance budgets
Time to Interactive 8.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Largest Contentful Paint element  
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Preconnect to required origins  
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
First Contentful Paint 5.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric

Does whitehouse.gov use compression?

Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on whitehouse.gov are reduced by 81%.
whitehouse.gov use gzip compression.
Original size: 181.88 KB
Compressed size: 33.88 KB
File reduced by: 148 KB (81%)

Google Safe Browsing

Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.
This site is not currently listed as suspicious

MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites. whitehouse.gov has 93 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  93
Safety Confidence:
  63
Child Safety Reputations:
  94
Child Safety Confidence:
  69

SSL Checker - SSL Certificate Verify

An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. whitehouse.gov supports HTTPS.
 whitehouse.gov supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: whitehouse.gov
Organization:
Location:
Issuer: R3
Valid from: Dec 21 08:50:21 2023 GMT
Valid until: Mar 20 08:50:20 2024 GMT
Authority: CA:FALSE
Keysize:
Common Name: R3
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Sep 4 00:00:00 2020 GMT
Valid until: Sep 15 16:00:00 2025 GMT
Authority: CA:TRUE
Keysize: 2048
Common Name: ISRG Root X1
Organization: Internet Security Research Group
Location: US
Issuer: DST Root CA X3
Valid from: Jan 20 19:14:03 2021 GMT
Valid until: Sep 30 18:14:03 2024 GMT
Authority: CA:TRUE
Keysize: 4096

Verify HTTP/2 Support

HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency.
 whitehouse.gov supports HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

Site Categories

Website categories are used to classify websites based on their content or purpose. These categories provide a way to organize and filter websites, allowing users to find relevant information or ensure compliance with specific regulations or policies.
Presidents/Obama
Executive Branch/President
Executive Office of the President/White House

Http Header

HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server.
server: nginx
date: Mon, 15 May 2023 15:55:09 GMT
content-type: text/html; charset=utf-8
content-length: 20
location: https://www.whitehouse.gov/
x-redirect-by: redirects.php
x-rq: mdw2 96 184 443
cache-control: max-age=300, must-revalidate
content-encoding: gzip
age: 1624
x-cache: hit
strict-transport-security: max-age=31536000;includeSubdomains;preload

HTTP/2 200 
server: nginx
date: Mon, 15 May 2023 15:55:09 GMT
content-type: text/html; charset=UTF-8
content-length: 34691
x-build-back-better: https://usds.gov/
x-frame-options: DENY
referrer-policy: strict-origin-when-cross-origin
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
content-security-policy: upgrade-insecure-requests
x-rq: mdw2 96 184 443
cache-control: max-age=300, must-revalidate
content-encoding: gzip
age: 216
x-cache: hit
vary: Accept-Encoding
accept-ranges: bytes
strict-transport-security: max-age=31536000;includeSubdomains;preload

DNS Lookup

DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.
Type Ip Target/Txt TTL
SOA 250
Mname 399e-adcs001.ede.pitc.gov
Rname postmaster.whitehouse.gov
Serial Number 2017022509
Refresh 300
Retry 300
Expire 604800
Minimum TTL 300
TXT 5q5ykzkfrtgfnb5jnn0vzbv78cdch558 10
TXT v=spf1 +mx include:spf.mandrillapp.com ip4:214.3.140.16/32 ip4:214.3.140.255/32 ip4:214.3.115.12/32 ip4:214.3.115.10/32 ip4:214.3.115.225/32 ip4:214.3.115.14/32 ip4:214.3.140.22/32 ~all 10
AAAA 2a04:fa87:fffd::c000:42a8 250
A 192.0.66.168 250
NS a1-61.akam.net 3550
NS a12-64.akam.net 3550
NS a5-64.akam.net 3550
NS a20-65.akam.net 3550
NS a3-67.akam.net 3550
NS a22-66.akam.net 3550

Whois Lookup

Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information.
WhoIs:
 

% DOTGOV WHOIS Server ready
   Domain Name: WHITEHOUSE.GOV
   Status: ACTIVE

>>> Last update of whois database: 2023-05-15T15:55:39Z