pizzatower.wiki Pizzatower.wiki

   
Pizza Tower Wiki

Domain Summary

What percent of global Internet users visit Pizzatower.wiki?

• 2.65E-5% of global Internet users visit Pizzatower.wiki

How many people visit Pizzatower.wiki each day?

• Pizzatower.wiki receives approximately 1.3K visitors and 9,171 page impressions per day.

Which countries does Pizzatower.wiki receive most of its visitors from?

• Pizzatower.wiki is mostly visited by people located in United States,Chile,Brazil.

How much Pizzatower.wiki can earn?

• Pizzatower.wiki should earn about $25.36/day from advertising revenue.

What is Pizzatower.wiki estimated value?

• Estimated value of Pizzatower.wiki is $25,039.58.

What IP addresses does Pizzatower.wiki resolve to?

• Pizzatower.wiki resolves to the IP addresses 2602:294::b13:0:0:0:110, 38.46.223.205.

Where are Pizzatower.wiki servers located in?

• Pizzatower.wiki has servers located in Draper, Utah, 84020, United States.

pizzatower.wiki Profile

Title:Pizza Tower Wiki Description:.
Category:Games / Video Games Consoles and Accessories
Edit Site Info

What technologies does pizzatower.wiki use?

These are the technologies used at pizzatower.wiki. pizzatower.wiki has a total of 7 technologies installed in 7 different categories.
Security
HSTS HSTS
hCaptcha hCaptcha
Wikis
MediaWiki MediaWiki
Web Servers
Nginx Nginx
Reverse proxies
Nginx Nginx
Miscellaneous
Open Graph Open Graph
Programming Languages
PHP PHP
Caching
Varnish Varnish

pizzatower.wiki Traffic Analysis

This website is viewed by an estimated 1.3K visitors daily, generating a total of 9.2K pageviews. This equates to about 39.7K monthly visitors. Pizzatower.wiki traffic has decreased by 29.43% compared to last month.
Daily Visitors1.3K
13.22%
Monthly Visits39.7K
29.43%
Pages per Visit7.01
22.95%
Visit duration03:55
43.28%
Bounce Rate31.49%
21.92%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
1,309
Monthly Visits:
39,663
Pages per Visit:
7.01
Daily Pageviews:
9,171
Avg. visit duration:
03:55
Bounce rate:
31.49%
Global Reach:
2.65E-5%
Monthly Visits (SEMrush):
62,607
Monthly Unique Visitors (SEMrush):
30,309
Monthly Visits (SimilarWeb):
39,661
HypeRank:
n/a
SEMrush Rank:
876,072
SimilarWeb Rank:
502,872
*All traffic values are estimates only.

Traffic sources

Direct:
50.01%
Referral:
0.93%
Search:
48.83%
Social:
0.15%
Paid:
0.07%

Desktop vs Mobile

Desktop:
21.16%
Mobile:
78.84%

Total Visits Last 3 Months

41.1K
DEC
56.2K
JAN
39.7K
FEB

Visitors by country

Country
Users%
 
United States 48.00%
 
Chile 38.60%
 
Brazil 7.85%
 
Mexico 2.08%
 
Argentina 2.06%

Which sites are competitors to pizzatower.wiki?

Websites similar to pizzatower.wiki are sites similar on user interests and browsing behavior. Users can discover new websites that are similar to the ones they already enjoy or find useful.
Domain
CompareDaily Visitors
roblox.com
Compare >20.4M
gx.games
Compare >50.7K
Last update was 82 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with pizzatower.wiki 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:
4

  ▼

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:
  pizzatower.wiki
Rank:
(Rank based on keywords, cost and organic traffic)
  876,072
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  191
Organic Traffic:
(Number of visitors coming from top 20 search results)
  1,341
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Full SEMrush Report >>

Revenue report ▼

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

How much would pizzatower.wiki make?

Daily Revenue:
$25.36
Monthly Revenue:
$760.80
Yearly Revenue:
$9,256.40
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 4,402$21.26
 
Chile 3,540$2.51
 
Brazil 720$0.96
 
Mexico 191$0.05
 
Argentina 189$0.05

Loss of money due to Adblock?

Daily Revenue Loss:
$4.22
Monthly Revenue Loss:
$126.68
Yearly Revenue Loss:
$1,541.33
Daily Pageviews Blocked:
1,339
Monthly Pageviews Blocked:
40,182
Yearly Pageviews Blocked:
488,875

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 792$3.83
 
Chile 460$0.33
 
Brazil 43$0.06
 
Argentina 26$0.01
 
Mexico 17$0.00

How much is pizzatower.wiki worth?

Website Value:
$25K

Ad Experience Report ▼

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

Mobile summary

Root domain:
pizzatower.wiki
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

Desktop summary

Root domain:
pizzatower.wiki
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 ▼

Summary of the abusive experience rating of a website.
Root domain:
pizzatower.wiki
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

Where is pizzatower.wiki hosted? ▼

Pizzatower.wiki may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
2602:294::b13:0:0:0:110, 38.46.223.205
ASN:
AS26042 
ISP:
TENEX Systems, Inc. 
Server Location:
Draper
Utah, UT
84020
United States, US
 

Other sites hosted on 38.46.223.205

How fast does pizzatower.wiki load? ▼

The average loading time of pizzatower.wiki is 572 ms. The Desktop speed index is 97 and mobile speed index is 87.
Average Load Time:
572 ms

Page Speed (Google PageSpeed Insights) - Desktop

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

Cumulative Layout Shift (CLS)13ms 66% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 66% 20% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 20% 13% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 13%
Time To First Byte (TTFB)1.3s 42% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 42% 47% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 47% 10% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 10%
First Contentful Paint (FCP)1.7s 77% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 77% 16% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 16% 5% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 5%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)37ms 98% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 98% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.8s 89% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 89% 7% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 7% 2% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 2%

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.

Cumulative Layout Shift (CLS)12ms 63% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 63% 23% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 23% 13% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 13%
Time To First Byte (TTFB)617ms 84% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 84% 12% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 12% 2% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)892ms 93% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 93% 4% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 4% 2% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 2%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)101ms 98% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 98% 1% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 1% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.1s 95% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 95% 3% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 3% 1% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 1%

Lab Data

Forced reflow  
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
Long critical network tree  
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
First Contentful Paint 0.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Time to Interactive 1.0 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
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
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
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. Learn more about optimal lazy loading
CSS Selector costs  
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
Total Blocking Time 20 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
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Largest Contentful Paint 0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Optimize DOM size  
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size

Page Speed (Google PageSpeed Insights) - Mobile

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

Cumulative Layout Shift (CLS)10ms 66% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 73% 14% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 14% 11% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 11%
Time To First Byte (TTFB)1.5s 42% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 35% 48% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 48% 16% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 16%
First Contentful Paint (FCP)2.1s 77% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 65% 24% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 24% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)104ms 98% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 89% 9% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 9% 0% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.2s 89% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 82% 13% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 13% 4% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 4%

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.

Cumulative Layout Shift (CLS)0ms 86% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 86% 6% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 6% 6% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 6%
Time To First Byte (TTFB)684ms 79% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 79% 14% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 14% 6% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 6%
First Contentful Paint (FCP)1.1s 89% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 89% 7% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 7% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)170ms 84% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 84% 14% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 14% 1% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.2s 93% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 93% 4% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 4% 1% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 1%

Lab Data

CSS Selector costs  
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
Forced reflow  
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
Speed Index 3.1 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
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Total Blocking Time 20 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
Optimize DOM size  
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size
Largest Contentful Paint 2.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
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Time to Interactive 4.5 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
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
First Contentful Paint 1.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Improve image delivery  
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
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. Learn more about optimal lazy loading
Long critical network tree  
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests

Does pizzatower.wiki 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 pizzatower.wiki are reduced by 82%.
pizzatower.wiki use gzip compression.
Original size: 88.15 KB
Compressed size: 15.26 KB
File reduced by: 72.88 KB (82%)

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.
Status:
  SAFE

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. pizzatower.wiki supports HTTPS.
 pizzatower.wiki supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: pizzatower.wiki
Organization:
Location:
Issuer: E5
Valid from: Feb 28 17:49:08 2025 GMT
Valid until: May 29 17:49:07 2025 GMT
Authority: CA:FALSE
Keysize:
Common Name: E5
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 GMT
Authority: CA:TRUE
Keysize:

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.
 pizzatower.wiki supports HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

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: Sun, 23 Mar 2025 23:29:22 GMT
content-type: text/html; charset=UTF-8
x-powered-by: PHP/8.2.28
x-content-type-options: nosniff
content-language: en
accept-ch: 
vary: Accept-Encoding, Cookie, Authorization
expires: Thu, 01 Jan 1970 00:00:00 GMT
cache-control: no-cache, no-store, max-age=0, must-revalidate
x-request-id: d348cb03a9231cfcf6513c5b
strict-transport-security: max-age=604800
x-served-by: mw201.wikitide.net
x-served-by: cp36.wikitide.net
xkey: pizzatower.wiki/
content-encoding: gzip
x-varnish: 438572157
age: 0
x-cache: cp36 pass
x-cache-status: pass
permissions-policy: interest-cohort=(), browsing-topics=()
content-security-policy: default-src 'self' *.miraheze.org *.mirabeta.org *.nexttide.org *.wikitide.org *.wikitide.net;  script-src blob: 'self' 'unsafe-inline' 'unsafe-eval' *.miraheze.org *.mirabeta.org *.nexttide.org *.wikitide.org *.wikitide.net *.wikimedia.org *.wikipedia.org *.wikibooks.org *.wiktionary.org *.wikiquote.org *.wikisource.org *.wikiversity.org *.wikinews.org *.wikivoyage.org mediawiki.org www.mediawiki.org wikidata.org www.gstatic.com www.google.com apis.google.com platform.twitter.com ajax.cloudflare.com cdnjs.cloudflare.com cdn.jsdelivr.net fastly.jsdelivr.net cdn.syndication.twimg.com openlayers.org www.gstatic.cn hcaptcha.com *.hcaptcha.com bandcamp.com flo.uri.sh challenges.cloudflare.com;  style-src 'self' data: 'unsafe-inline' miraheze.org wikitide.org *.miraheze.org *.mirabeta.org *.nexttide.org *.wikitide.org *.wikitide.net *.wikimedia.org *.wikipedia.org *.wikibooks.org *.wiktionary.org *.wikiquote.org *.wikisource.org *.wikiversity.org *.wikinews.org *.wikivoyage.org mediawiki.org www.mediawiki.org wikidata.org www.gstatic.com fonts.googleapis.com cdn.jsdelivr.net fastly.jsdelivr.net cdnjs.cloudflare.com platform.twitter.com ton.twimg.com hcaptcha.com *.hcaptcha.com use.typekit.net;  img-src blob: 'self' data: miraheze.org wikitide.org *.miraheze.org *.mirabeta.org *.nexttide.org *.wikitide.org *.wikitide.net upload.wikimedia.org wikimedia.org maps.google.com www.gstatic.com maxcdn.bootstrapcdn.com *.twimg.com i.imgur.com image.tmdb.org *.googleusercontent.com *.fontawesome.com *.dropboxstatic.com *.redd.it *.redditmedia.com mirrors.creativecommons.org www.gnu.org live.staticflikr.com cdn.pixabay.com cdn.geogebra.org docs.blender.org *.imgbox.com tile.openstreetmap.org *.tile.openstreetmap.org cdn.discordapp.com na.llnet.sims3storee.cdn.ea.com *.fastly.net minotar.net db.onlinewebfonts.com openlayers.org discordapp.com imgbb.com postimages.org platform.twitter.com syndication.twitter.com img.newspapers.com cdn.smutstone.com storage.googleapis.com *.fbcdn.net i.ytimg.com *.imgbb.com simgbb.com *.simgbb.com ibb.co *.ibb.co *.postimages.org postimgs.org *.postimgs.org postimg.cc *.postimg.cc *.rbxcdn.com cms-imgp.jw-cdn.org hosted.weblate.org;  font-src 'self' data: *.miraheze.org *.mirabeta.org *.nexttide.org *.wikitide.org *.wikitide.net fonts.gstatic.com fonts.googleapis.com cdnjs.cloudflare.com cdn.jsdelivr.net fastly.jsdelivr.net db.onlinewebfonts.com upload.wikimedia.org use.typekit.net;  media-src 'self' blob: *.miraheze.org *.mirabeta.org *.nexttide.org *.wikitide.org *.wikitide.net upload.wikimedia.org embed.nicovideo.jp *.youtube.com *.youtube-nocookie.com player.twitch.tv clips.twitch.tv player.vimeo.com apis.google.com bandcamp.com;  frame-src 'self' *.miraheze.org *.mirabeta.org *.nexttide.org *.wikitide.org *.wikitide.net www.google.com docs.google.com apis.google.com calendar.google.com drive.google.com web.libera.chat snap.berkeley.edu *.youtube-nocookie.com www.youtube.com player.twitch.tv platform.twitter.com discord.com discordapp.com embed.nicovideo.jp syndication.twitter.com open.spotify.com www.gofundme.com archive.org w.soundcloud.com query.wikidata.org player.vimeo.com www.bing.com lucid.app scratch.mit.edu hcaptcha.com *.hcaptcha.com bandcamp.com challenges.cloudflare.com;  connect-src 'self' blob: *.miraheze.org *.mirabeta.org *.nexttide.org *.wikitide.org *.wikitide.net www.wikidata.org *.wikipedia.org www.mediawiki.org *.wikimedia.org *.wikinews.org *.wiktionary.org cdn.jsdelivr.net storage.googleapis.com *.youtube-nocookie.com hcaptcha.com *.hcaptcha.com 1.1.1.1 translate.googleapis.com games.roblox.com economy.roblox.com;
strict-transport-security: max-age=604800

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
AAAA 2602:294::b13:0:0:0:110 68
A 38.46.223.205 68
NS ns2.miraheze.org 3518
NS ns1.miraheze.org 3518
HINFO 3600

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. Domain registration for this website began on June 16, 2024 and will expire on June 16, 2026 if not renewed. This website is now assigned through the registrar ENOM, INC.. The WHOIS data for this website's domain was last updated on September 4, 2024.
Domain Created:
2024-06-16
Domain Expires:
2026-06-16
Domain Updated:
2024-09-04
Domain Age:
28 days
Domain Registrar:
ENOM, INC.
Domain Owner:
Proxy Protection LLC
WhoIs:
 


Domain Name: pizzatower.wiki
Registry Domain ID: D5A427AC4A26B42E283AA753C72462670-GDREG
Registrar WHOIS Server: WHOIS.ENOM.COM
Registrar URL: WWW.ENOMDOMAINS.COM
Updated Date: 2024-09-04T18:36:08.80Z
Creation Date: 2024-06-16T17:52:00.00Z
Registrar Registration Expiration Date: 2026-06-16T17:52:00.00Z
Registrar: ENOM, INC.
Registrar IANA ID: 48
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registrant Name: Proxy Protection LLC (349371383)
Registrant Organization: Proxy Protection LLC
Registrant Street: 417 Associated Rd #327
Registrant Street: C/O pizzatower.wiki
Registrant City: Brea
Registrant State/Province: CA
Registrant Postal Code: 92821
Registrant Country: US
Registrant Phone: +1.7147064182
Registrant Phone Ext: 
Registrant Fax: 
Registrant Email: email
Admin Name: Proxy Protection LLC
Admin Organization: Proxy Protection LLC
Admin Street: 417 Associated Rd #327
Admin Street: C/O pizzatower.wiki
Admin City: Brea
Admin State/Province: CA
Admin Postal Code: 92821
Admin Country: US
Admin Phone: +1.7147064182
Admin Phone Ext: 
Admin Fax: 
Admin Email: email
Tech Name: Proxy Protection LLC
Tech Organization: Proxy Protection LLC
Tech Street: 417 Associated Rd #327
Tech Street: C/O pizzatower.wiki
Tech City: Brea
Tech State/Province: CA
Tech Postal Code: 92821
Tech Country: US
Tech Phone: +1.7147064182
Tech Phone Ext: 
Tech Fax: 
Tech Email: email
Name Server: NS1.MIRAHEZE.ORG
Name Server: NS2.MIRAHEZE.ORG
DNSSEC: unsigned
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.4259744689
URL of the ICANN WHOIS Data Problem Reporting System: HTTP://WDPRS.INTERNIC.NET/
>>> Last update of WHOIS database: 2025-03-23T23:30:42.00Z