Jstor.org
JSTOR Home
Domain Summary
What is the traffic rank for Jstor.org?
• Jstor.org ranks #9,200 globally on HypeStat.
What percent of global Internet users visit Jstor.org?
• 0.0564% of global Internet users visit Jstor.org
How many people visit Jstor.org each day?
• Jstor.org receives approximately 0.9M visitors and 1,693,003 page impressions per day.
Which countries does Jstor.org receive most of its visitors from?
• Jstor.org is mostly visited by people located in United States,India,Canada.
How much Jstor.org can earn?
• Jstor.org should earn about $4,808.96/day from advertising revenue.
What is Jstor.org estimated value?
• Estimated value of Jstor.org is $5,536,595.84.
What IP addresses does Jstor.org resolve to?
• Jstor.org resolves to the IP addresses 151.101.192.152.
Where are Jstor.org servers located in?
• Jstor.org has servers located in San Francisco, CA, 94107, United States.
jstor.org Profile
Title:JSTOR Home
Tags:
About:
Scans of print journals, with 10 major math journals (requires subscription).
JSTOR is a digital library of academic journals, books, and primary sources. Edit Site Info
JSTOR is a digital library of academic journals, books, and primary sources. Edit Site Info
What technologies does jstor.org use?
These are the technologies used at jstor.org. jstor.org has a total of 9 technologies installed in 9 different categories.
jstor.org Traffic Analysis
Jstor.org is ranked #9,200 in the world. This website is viewed by an estimated 0.9M visitors daily, generating a total of 1.7M pageviews. This equates to about 28M monthly visitors.Daily Visitors0.9M
Monthly Visits28M
Pages per Visit1.83
Visit duration05:20
Bounce Rate59.77%
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- 925,138
- Monthly Visits:
- 28,031,681
- Pages per Visit:
- 1.83
- Daily Pageviews:
- 1,693,003
- Avg. visit duration:
- 05:20
- Bounce rate:
- 59.77%
- Global Reach:
- 0.0564%
- Monthly Visits (SEMrush):
- 27,261,244
- Monthly Unique Visitors (SEMrush):
- 16,718,268
- Monthly Visits (SimilarWeb):
- 27,754,141
- HypeRank:
- 9,200
- SEMrush Rank:
- 1,418
Traffic sources
- Direct:
- 25.00%
- Referral:
- 10.36%
- Search:
- 63.79%
- Social:
- 0.84%
- Paid:
- 0%
Visitors by country
- Country
- Users%
- United States 26.3%
- India 9.5%
- Canada 4.1%
- United Kingdom 3.4%
- Philippines 3.3%
Where do visitors go on jstor.org?
- Reach%Pageviews%PerUser
- jstor.org
- 97.24%92.65%1.80
- daily.jstor.org
- 2.12%5.14%4.6
- about.jstor.org
- 1.00%0.59%1.1
- support.jstor.org
- 0.28%0.21%1
- guides.jstor.org
- 0.11%0.18%3
Backlinks Report ▼
Jstor.org has a total of 252,448 backlinks from 2,114 referring domains and most of them comes from United States.- Total Backlinks:
- 252,448
- Follow Links:
- 210,563
- Nofollow Links:
- 41,884
- Referring Domains:
- 2,114
- Referring IPs:
- 2,457
- Authority Domain Score:
- 63
Backlinks by country
- Country
- Domains
- United States 1,710
- Germany 125
- France 85
- United Kingdom 62
- Russian Federation 52
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 939
- .org
- 206
- .net
- 113
- .ru
- 85
- .gov
- 7
Last update was 1434 days ago
This can take up to 60 seconds. Please wait...
This can take up to 60 seconds. Please wait...
*HypeStat.com is not promoting or affiliated with jstor.org 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:
- 9,490,000
- Bing Index:
- 1,310,000
Moz Data ▼
Domain Authority (DA) is a metric developed by Moz. DA is a score that predicts the ranking potential of a website on search engine result pages (SERPs). Moz calculates Domain Authority on a logarithmic scale from 1 to 100, with higher scores indicating a greater likelihood of ranking well in search results. Moz Domain Authority of jstor.org is 91.- Domain Authority:
- 91
- Page Authority:
- 65
- MozRank:
- 6
▼
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.- Domain:
- jstor.org
- Rank:
(Rank based on keywords, cost and organic traffic) - 1,418
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 5,710,817
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 2,685,482
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $1,722,089.00
Revenue report ▼
Google.com would generate approximately $4.8K per day if the source of income were advertisements, which equates to an estimated monthly revenue of $144.3K and annual gross revenue of approximately $1.8M. Based on these figures, the site's net worth is estimated at around $5.5M.How much would jstor.org make?
- Daily Revenue:
- $4,808.96
- Monthly Revenue:
- $144,268.80
- Yearly Revenue:
- $1,755,270.40
Daily earning by country
- CountryPageviewsEarning
- India 152,370$57.90
- Egypt 0$0.00
- Indonesia 0$0.00
- Singapore 0$0.00
- Turkey 0$0.00
Loss of money due to Adblock?
- Daily Revenue Loss:
- $601.65
- Monthly Revenue Loss:
- $18,049.38
- Yearly Revenue Loss:
- $219,600.74
- Daily Pageviews Blocked:
- 193,002
- Monthly Pageviews Blocked:
- 5,790,070
- Yearly Pageviews Blocked:
- 70,445,855
Daily revenue loss by country
- CountryBlockedLost Money
- India 42,664$16.21
- Egypt 0$0.00
- Indonesia 0$0.00
- Singapore 0$0.00
- Turkey 0$0.00
How much is jstor.org worth?
- Website Value:
- $5.5M
Ad Experience Report ▼
Summary of the ad experience rating of a website for a specific platform.Mobile summary
- Root domain:
- jstor.org
- Last Change Time:
(The last time that the site changed status.) - 2020-02-25 10:35:05
- 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:
- jstor.org
- Last Change Time:
(The last time that the site changed status.) - 2020-02-25 10:35:05
- 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:
- jstor.org
- Last Change Time:
(The last time that the site changed status.) - 2020-02-25 10:35:05
- 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 jstor.org hosted? ▼
Jstor.org may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.- Server IP:
- 151.101.192.152
- ASN:
- AS54113
- ISP:
- Fastly
- Server Location:
- San Francisco
CA
94107
United States, US
Other sites hosted on 151.101.192.152
How fast does jstor.org load? ▼
The average loading time of jstor.org is 2428 ms. The Desktop speed index is 71 and mobile speed index is 58.- Average Load Time:
- 2428 ms
Page Speed (Google PageSpeed Insights) - Desktop
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
Time To First Byte (TTFB)0
First Contentful Paint (FCP)2.8s
First Input Delay (FID)4ms
Interaction To Next Paint (INP)0
Largest Contentful Paint (LCP)3.6s
Origin Data
All pages served from this origin have an SLOW 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)39ms
Time To First Byte (TTFB)0
First Contentful Paint (FCP)3.2s
First Input Delay (FID)4ms
Interaction To Next Paint (INP)0
Largest Contentful Paint (LCP)4.2s
Lab Data
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
The maximum potential First Input Delay that your users could experience is the duration of the longest task. 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
First Contentful Paint marks the time at which the first text or image is painted. Learn more
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
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
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn more
Animations which are not composited can be janky and increase CLS. Learn more
First CPU Idle 2.1 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. . Learn more
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. . 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
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 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
First Meaningful Paint 1.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
First Meaningful Paint measures when the primary content of a page is visible. Learn more
Largest Contentful Paint 3.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Largest Contentful Paint marks the time at which the largest 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
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Time to Interactive 2.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Speed Index 1.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a SLOW 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)0
Time To First Byte (TTFB)0
First Contentful Paint (FCP)9.1s
First Input Delay (FID)129ms
Interactive To Next Paint (INP)0
Largest Contentful Paint (LCP)0
Origin Data
All pages served from this origin have an SLOW 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)0
Time To First Byte (TTFB)0
First Contentful Paint (FCP)7.6s
First Input Delay (FID)261ms
Interactive To Next Paint (INP)0
Largest Contentful Paint (LCP)0
Lab Data
First Meaningful Paint 3.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
First Meaningful Paint measures when the primary content of a page is visible. Learn more
Max Potential First Input Delay 280 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more
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 7.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Total Blocking Time 490 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 80 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
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
First Contentful Paint (3G) 6381 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more
Speed Index 5.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
First CPU Idle 6.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 CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. . Learn more
First Contentful Paint 3.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
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
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Does jstor.org 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 jstor.org are reduced by 73%.
jstor.org use gzip compression.
Original size: 32.92 KB
Compressed size: 8.6 KB
File reduced by: 24.32 KB (73%)
Compressed size: 8.6 KB
File reduced by: 24.32 KB (73%)
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. jstor.org has 94 Safety Reputations.- Status:
- SAFE
- Safety Reputations:
- 94
- Safety Confidence:
- 55
- Child Safety Reputations:
- 94
- Child Safety Confidence:
- 53
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. jstor.org supports HTTPS. jstor.org supports HTTPS
Verifying SSL Support. Please wait...
Common Name: www.jstor.org
Organization: Ithaka Harbors, Inc.
Location: Ann Arbor, Michigan, US
Issuer: GlobalSign CloudSSL CA - SHA256 - G3
Valid from: Jan 2 23:05:44 2019 GMT
Valid until: Apr 6 23:05:44 2021 GMT
Authority: Is not a CA
Keysize:
Organization: Ithaka Harbors, Inc.
Location: Ann Arbor, Michigan, US
Issuer: GlobalSign CloudSSL CA - SHA256 - G3
Valid from: Jan 2 23:05:44 2019 GMT
Valid until: Apr 6 23:05:44 2021 GMT
Authority: Is not a CA
Keysize:
Common Name: GlobalSign CloudSSL CA - SHA256 - G3
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign Root CA
Valid from: Aug 19 00:00:00 2015 GMT
Valid until: Aug 19 00:00:00 2025 GMT
Authority: Is a CA
Keysize: 2048 Bits
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign Root CA
Valid from: Aug 19 00:00:00 2015 GMT
Valid until: Aug 19 00:00:00 2025 GMT
Authority: Is a CA
Keysize: 2048 Bits
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. jstor.org 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.- Math/Publications
- Publications/Directories
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: Varnish
Retry-After: 0
Location: http://www.jstor.org/
Connection: keep-alive
Content-Length: 58
Accept-Ranges: bytes
Date: Wed, 02 Dec 2020 14:05:38 GMT
Via: 1.1 varnish
X-Served-By: cache-pwk4965-PWK
X-Cache: HIT
X-Cache-Hits: 0
HTTP/1.1 301 Permanent Redirect
Server: Varnish
Retry-After: 0
Location: https://www.jstor.org/
Connection: keep-alive
Content-Length: 59
Accept-Ranges: bytes
Date: Wed, 02 Dec 2020 14:05:38 GMT
Via: 1.1 varnish
X-Served-By: cache-lax10623-LGB
X-Cache: HIT
X-Cache-Hits: 0
HTTP/2 200
server: Apache/2.4.29 (Ubuntu)
x-frame-options: SAMEORIGIN
set-cookie: AccessSession=H4sIAAAAAAAAAJ2RS2_bMBCE7_kVgs6hwcfysb3ZSt0GLXppbkFQrCgSVaEkhiUFKIL899IUHcNpc-mR38wOh8vni6qq-66uPlQ150qRaqOPWgEiko4AneVKA1BLUF8ezL64e_KMiHjBvwp2gqttg0Kj3GwlXjVabj42YiubLcjGrBf3vrhJo0NI8Uq3QFZgJAKjQVrFVUCxuOe52G0Eb1ybLo4tZ6A6zcjYjgGClSnIGBmWEZqnn4eRSMMYMnmiYUkRhhsUaJXTqLPU73K6sSsp5Eo4uxLclJzuvn84DxrHx3Mw-fMzeT-NB3RbPafzacGCc445N7HSpoYjCAUgQqsUahbTD6SnSc6co8AkdtEJ56Pq6Dgz_d6FPPRp_zjvXqNf8YbG3i9akl4u_1FIvS0k_yoUHLdd8Cwq2zLwNm3dO8m4Fy5V9C0n_p-FqrtlpdPpYyyePmag94T5HYGmaZ93Xx7aNPnab-tjleYmgwfahf1TPwzhx_XXo_Z90a5vPq-_rHO_i5c_-7kFJCEDAAA; Path=/; SameSite=Lax; Secure
set-cookie: AccessSessionSignature=aef527e2556aa9a43085646b82a5b3907dab834ea73ecf09bb8e70ad56414a24; Path=/; SameSite=Lax; Secure
set-cookie: AccessSessionTimedSignature=e1aac846ece5ddc53b6cc164b2c63918b675bf67a3ed1a8c6c6723ef29e12ff6; Path=/; SameSite=Lax; Secure
set-cookie: UUID=7f4c68bc-afb0-43d5-a67d-49472894662e; expires=Sat, 02 Dec 2023 14:05:38 GMT; Max-Age=94608000; Path=/; SameSite=None; Secure
set-cookie: csrftoken=L2O2CfGq0zcNQFcrM5EQIGnB2wq04XNbFdpfocDe0vBvPNaRibu8vRYMKtjF1sWz; expires=Wed, 01 Dec 2021 14:05:38 GMT; Max-Age=31449600; Path=/; SameSite=Lax; Secure
set-cookie: ReferringRequestId=search:def6faf8bf8fe554f2cdf445faea0082; Path=/; SameSite=Lax; Secure
set-cookie: ADRUM_BT=R:20|n:Ithaka_20fb118f-0305-4128-b6c9-ee5f3357d8aa|g:cf799369-c8bf-4367-8aee-7f3c98756197|i:128934|e:77; Max-Age=30; Path=/; Secure
content-encoding: gzip
content-type: text/html; charset=utf-8
x-jstor-restarts: 0
accept-ranges: bytes
date: Wed, 02 Dec 2020 14:05:38 GMT
via: 1.1 varnish
x-served-by: cache-lax10638-LGB
x-cache: MISS
x-cache-hits: 0
x-timer: S1606917938.490767,VS0,VE185
vary: Cookie,Accept-Encoding,Fastly-SSL,Origin,X-Requested-Host
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 |
| TXT | 3600 | ||
| TXT | 3600 | ||
| TXT | 3600 | ||
| TXT | 3600 | ||
| TXT | 3600 | ||
| MX | 3600 | ||
| MX | 3600 | ||
| SOA | 3600 | ||
| Mname | usnjpr2ns02.ithaka.org | ||
| Rname | hostmaster.ithaka.org | ||
| Serial Number | 2020113001 | ||
| Refresh | 10800 | ||
| Retry | 3600 | ||
| Expire | 1209600 | ||
| Minimum TTL | 3600 | ||
| A | 151.101.128.152 | 3555 | |
| A | 151.101.192.152 | 3555 | |
| A | 151.101.64.152 | 3555 | |
| A | 151.101.0.152 | 3555 | |
| NS | 3555 | ||
| NS | 3555 | ||
| NS | 3555 | ||
| NS | 3555 | ||
| NS | 3555 |
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 February 16, 1996 and will expire on November 5, 2024 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on November 5, 2024.- Domain Created:
- 1996-02-16
- Domain Age:
- 28 years 8 months 18 days
- WhoIs:
whois lookup at whois.pir.org...Domain Name: JSTOR.ORG Registry Domain ID: D1217247-LROR Registrar WHOIS Server: whois.networksolutions.com Registrar URL: http://www.networksolutions.com Updated Date: 2019-09-04T20:21:44Z Creation Date: 1996-02-16T05:00:00Z Registry Expiry Date: 2021-02-17T05:00:00Z Registrar Registration Expiration Date: Registrar: Network Solutions, LLC Registrar IANA ID: 2 Registrar Abuse Contact Email:Registrar Abuse Contact Phone: +1.8003337680 Reseller: Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registrant Organization: Ithaka Harbors, Inc. Registrant State/Province: FL Registrant Country: US Name Server: USNJPR2NS02.ITHAKA.ORG Name Server: USNJPR1NS01.ITHAKA.ORG Name Server: USMIAA1NS03.ITHAKA.ORG Name Server: USNJPR2NS04.ITHAKA.ORG Name Server: AA2NS13.ITHAKA.ORG DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/) >>> Last update of WHOIS database: 2020-12-02T14:05:20Z <<< For more information on Whois status codes, please visit https://icann.org/epp Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data 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 data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.