Pizzagate.Pizza - Info pizzagate.pizza

pizzagate.pizza receives about 136 unique visitors and 136 (1.00 per visitor) page views per day which should earn about $0.56/day from advertising revenue. Estimated site value is $405.32. According to Alexa Traffic Rank pizzagate.pizza is ranked number 6,841,478 in the world and 3.0E-6% of global Internet users visit it. Site is hosted in Houston, Texas, 77092, United States and links to network IP address 108.167.182.40. This server supports HTTPS and HTTP/2.

About - pizzagate.pizza


Technologies used on Website

Web Servers
Apache
Analytics
Clicky

pizzagate.pizza Profile

Title: PizzaGate
Last update was 138 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is pizzagate.pizza?

136 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
136
Monthly Unique Visitors:
3,264
Pages per Visit:
1.00
Daily Pageviews:
136
Alexa Rank:
6,841,478 visit alexa
Alexa Reach:
3.0E-6%   (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

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  pizzagate.pizza
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
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 pizzagate.pizza?

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:
pizzagate.pizza
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:
pizzagate.pizza
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 pizzagate.pizza can earn?

Daily Revenue:
$0.56
Monthly Revenue:
$16.80
Yearly Revenue:
$204.40
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do pizzagate.pizza lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is pizzagate.pizza worth?

Website Value:
$405.32

+ Where is pizzagate.pizza hosted?

Server IP:
108.167.182.40
ASN:
AS46606 
ISP:
Unified Layer 
Server Location:
Houston
Texas, TX
77092
United States, US
 

Other sites hosted on 108.167.182.40

+ How fast does pizzagate.pizza load?

Average Load Time:
n/a ms n/a % 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

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.
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 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.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 33 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
33
Maximum DOM Depth
5
Maximum Child Elements
21
Keep request counts low and transfer sizes small - 5 requests • 81 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
581 KB
Image
172 KB
Script
27 KB
Document
11 KB
Stylesheet
11 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
27 KB
Eliminate render-blocking resources - Potential savings of 190 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
http://pizzagate.pizza/pzgt.css
1 KB70
http://static.getclicky.com/js
6 KB190
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://pizzagate.pizza/
0 ms335 ms1 KB2 KB200text/htmlDocument
http://pizzagate.pizza/pzgt.css
349 ms504 ms1 KB1 KB200text/cssStylesheet
http://static.getclicky.com/js
350 ms387 ms6 KB15 KB200text/javascriptScript
http://pizzagate.pizza/pizzagate-scandal.png
350 ms533 ms72 KB72 KB200image/pngImage
http://in.getclicky.com/in.php?site_id=101008011&type=pageview&href=%2F&title=PizzaGate&res=800x600&lang=en&jsuid=1359832167&mime=js&x=0.8985265159822844
722 ms750 ms1 KB0 KB200text/javascriptScript
Serve static assets with an efficient cache policy - 3 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://pizzagate.pizza/pizzagate-scandal.png
0 ms72 KB
http://pizzagate.pizza/pzgt.css
0 ms1 KB
http://static.getclicky.com/js
604800000 ms6 KB
Minimize third-party usage - Third-party code blocked the main thread for 0 ms
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.

Third-Party
SizeMain-Thread Blocking Time
7 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
361 ms
9 ms
529 ms
11 ms
541 ms
31 ms
578 ms
19 ms
732 ms
14 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
86 ms3 ms1 ms
Avoids enormous network payloads - Total size was 81 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://pizzagate.pizza/pizzagate-scandal.png
72 KB
http://static.getclicky.com/js
6 KB
http://pizzagate.pizza/
1 KB
http://in.getclicky.com/in.php?site_id=101008011&type=pageview&href=%2F&title=PizzaGate&res=800x600&lang=en&jsuid=1359832167&mime=js&x=0.8985265159822844
1 KB
http://pizzagate.pizza/pzgt.css
1 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
32 ms
Rendering
21 ms
Other
21 ms
Script Evaluation
18 ms
Parse HTML & CSS
9 ms
Script Parsing & Compilation
3 ms
Serve images in next-gen formats - Potential savings of 53 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
http://pizzagate.pizza/pizzagate-scandal.png
72 KB53 KB
Avoid chaining critical requests - 2 chains 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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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 340 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.

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.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. 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.


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

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.
First Contentful Paint (3G) 2460 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. 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.
Speed Index 1.4 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.
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 40 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Minimize third-party usage - Third-party code blocked the main thread for 0 ms
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.

Third-Party
SizeMain-Thread Blocking Time
7 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
392 ms
9 ms
552 ms
16 ms
750 ms
11 ms
JavaScript execution time - 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.

URL
Total CPU TimeScript EvaluationScript Parse
Other
172 ms11 ms5 ms
http://static.getclicky.com/js
51 ms45 ms6 ms
Avoids enormous network payloads - Total size was 81 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://pizzagate.pizza/pizzagate-scandal.png
72 KB
http://static.getclicky.com/js
6 KB
http://pizzagate.pizza/
1 KB
http://in.getclicky.com/in.php?site_id=101008011&type=pageview&href=%2F&title=PizzaGate&res=412x660&lang=en&jsuid=888018637&mime=js&x=0.1402273356422561
1 KB
http://pizzagate.pizza/pzgt.css
1 KB
Minimizes main-thread work - 0.2 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
Other
71 ms
Style & Layout
62 ms
Script Evaluation
60 ms
Parse HTML & CSS
14 ms
Script Parsing & Compilation
12 ms
Rendering
10 ms
Serve images in next-gen formats - Potential savings of 53 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
http://pizzagate.pizza/pizzagate-scandal.png
72 KB53 KB
Avoids an excessive DOM size - 33 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
33
Maximum DOM Depth
5
Maximum Child Elements
21
Keep request counts low and transfer sizes small - 5 requests • 81 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
581 KB
Image
172 KB
Script
27 KB
Document
11 KB
Stylesheet
11 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
27 KB
Eliminate render-blocking resources - Potential savings of 600 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
http://pizzagate.pizza/pzgt.css
1 KB180
http://static.getclicky.com/js
6 KB630
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://pizzagate.pizza/
0 ms361 ms1 KB2 KB200text/htmlDocument
http://pizzagate.pizza/pzgt.css
376 ms518 ms1 KB1 KB200text/cssStylesheet
http://static.getclicky.com/js
377 ms411 ms6 KB15 KB200text/javascriptScript
http://pizzagate.pizza/pizzagate-scandal.png
377 ms620 ms72 KB72 KB200image/pngImage
http://in.getclicky.com/in.php?site_id=101008011&type=pageview&href=%2F&title=PizzaGate&res=412x660&lang=en&jsuid=888018637&mime=js&x=0.1402273356422561
732 ms762 ms1 KB0 KB200text/javascriptScript
Serve static assets with an efficient cache policy - 3 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://pizzagate.pizza/pizzagate-scandal.png
0 ms72 KB
http://pizzagate.pizza/pzgt.css
0 ms1 KB
http://static.getclicky.com/js
604800000 ms6 KB
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.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. 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 - 2 chains 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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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 360 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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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

Your page has 1 blocking script resources and 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.Use asynchronous versions of the following scripts:

http://static.getclicky.com/js
Optimize CSS Delivery of the following:

http://pizzagate.pizza/pzgt.css

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 63% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response:

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Aaric S. Eisenstein and 2 others render only 6 pixels tall (16 CSS pixels) .
(May 14, 2009 1:59 PM): and 2 others render only 6 pixels tall (16 CSS pixels) .
from Chicago f…same channels? and 4 others render only 6 pixels tall (16 CSS pixels) .
pizza/dogs and 1 others render only 6 pixels tall (16 CSS pixels) .

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://pizzagate.pizza/pizzagate-scandal.png (expiration not specified)
http://pizzagate.pizza/pzgt.css (expiration not specified)

Optimize images

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

Optimize the following images to reduce their size by 9.3KiB (13% reduction).

Compressing http://pizzagate.pizza/pizzagate-scandal.png could save 9.3KiB (13% reduction).

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 141B (13% reduction).

Minifying http://pizzagate.pizza/ could save 141B (13% reduction) after compression.
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.
Enable compression
You have compression enabled. Learn more about enabling compression.
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 JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does pizzagate.pizza use compression?

pizzagate.pizza use gzip compression.
Original size: 2.23 KB
Compressed size: 1.12 KB
File reduced by: 1.12 KB (49%)

+ 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

pizzagate.pizza supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: pizzagate.pizza
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Nov 30 19:39:32 2019 GMT
Valid until: Feb 28 19:39:32 2020 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

pizzagate.pizza supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Upgrade: h2c
Connection: Upgrade

HTTP/2 200 
date: Thu, 01 Jan 1970 00:00:00 GMT
server: Apache
vary: Accept-Encoding
content-encoding: gzip
content-length: 1144
content-type: text/html; charset=UTF-8

+ DNS Lookup

Type Ip Target TTL
SOA 3600
Mname ns8413.hostgator.com
Rname root.gator4207.hostgator.com
Serial Number 2018060900
Refresh 86400
Retry 7200
Expire 3600000
Minimum TTL 0
MX mail.pizzagate.pizza 3600
TXT 3600
A 108.167.182.40 3582
NS ns8413.hostgator.com 3582
NS ns8414.hostgator.com 3582

+ Whois Lookup

Domain Created:
2016-12-02
Domain Age:
3 years 1 months 15 days  
WhoIs:
 

whois lookup at whois.donuts.co...
Domain Name: pizzagate.pizza
Registry Domain ID: 8024cad78cd241649cd8f16e88ca36ef-DONUTS
Registrar WHOIS Server: whois.godaddy.com/
Registrar URL: http://www.godaddy.com/domains/search.aspx?ci=8990
Updated Date: 2020-01-16T04:15:32Z
Creation Date: 2016-12-02T04:15:22Z
Registry Expiry Date: 2020-12-02T04:15:22Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Domains By Proxy, LLC
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: Arizona
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns8413.hostgator.com
Name Server: ns8414.hostgator.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2020-01-18T00:15:19Z <<<

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

Terms of Use: Donuts Inc. provides this Whois service for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Donuts does not guarantee its accuracy. Users accessing the Donuts Whois service agree to use the data only for lawful purposes, and under no cir***stances may this data be used to: a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the registrar’s own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Donuts or any ICANN-accredited registrar, except as reasonably necessary to register domain names or modify existing registrations. When using the Donuts Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data can be requested by submitting a request via the form found at https://donuts.domains/about/policies/whois-layered-access/ Donuts Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
Last update was 138 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

dezdoes.com
23 secs
somoyekhon.net
44 secs
post.rm.dk
52 secs
somoydharanews.com
1 min
post.regionsjaelland.dk
1 min
somoybangla.tv
2 mins
pos.lycamobile.es
2 mins
softwaregighub.com
3 mins
somoy.news
3 mins
webpaliz.com
3 mins
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!
pizzagate.pizza widget