zadzmo.org Zadzmo.org

   
ZADZMO organization

Domain Summary

What is the traffic rank for Zadzmo.org?

• Zadzmo.org ranks #827,579 globally on HypeStat.

What percent of global Internet users visit Zadzmo.org?

• 2.43E-5% of global Internet users visit Zadzmo.org

How many people visit Zadzmo.org each day?

• Zadzmo.org receives approximately 1.2K visitors and 2,837 page impressions per day.

Which countries does Zadzmo.org receive most of its visitors from?

• Zadzmo.org is mostly visited by people located in United States,Japan,Austria.

How much Zadzmo.org can earn?

• Zadzmo.org should earn about $10.32/day from advertising revenue.

What is Zadzmo.org estimated value?

• Estimated value of Zadzmo.org is $11,255.85.

What IP addresses does Zadzmo.org resolve to?

• Zadzmo.org resolves to the IP addresses 2602:f977:800::e076:63ff:fe88:2d24, 166.84.136.36.

Where are Zadzmo.org servers located in?

• Zadzmo.org has servers located in United States.

zadzmo.org Profile

Title:ZADZMO organization
Edit Site Info

What technologies does zadzmo.org use?

These are the technologies used at zadzmo.org. zadzmo.org has a total of 2 technologies installed in 3 different categories.
Security
HSTS HSTS
Web Servers
Nginx Nginx
Reverse proxies
Nginx Nginx

zadzmo.org Traffic Analysis

Zadzmo.org is ranked #827,579 in the world. This website is viewed by an estimated 1.2K visitors daily, generating a total of 2.8K pageviews. This equates to about 36.3K monthly visitors. Zadzmo.org traffic has decreased by 93% compared to last month.
Daily Visitors1.2K
93.05%
Monthly Visits36.3K
93%
Pages per Visit2.37
32.23%
Visit duration01:35
60%
Bounce Rate42.71%
33.94%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
1,197
Monthly Visits:
36,269
Pages per Visit:
2.37
Daily Pageviews:
2,837
Avg. visit duration:
01:35
Bounce rate:
42.71%
Global Reach:
2.43E-5%
Monthly Visits (SEMrush):
4,153
Monthly Unique Visitors (SEMrush):
4,010
Monthly Visits (SimilarWeb):
35,205
HypeRank:
827,579
SEMrush Rank:
24,161,392
SimilarWeb Rank:
827,579
*All traffic values are estimates only.

Traffic sources

Direct:
27.02%
Referral:
71.49%
Search:
0%
Social:
1.49%
Paid:
0%

Desktop vs Mobile

Desktop:
100.00%
Mobile:
0%

Total Visits Last 3 Months

0
DEC
518.1K
JAN
36.3K
FEB

Visitors by country

Country
Users%
 
United States 55.37%
 
Japan 14.65%
 
Austria 13.98%
 
United Kingdom 7.25%
 
Canada 3.97%
Last update was 90 days ago
     
This can take up to 60 seconds. Please wait...

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

  ▼

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:
  zadzmo.org
Rank:
(Rank based on keywords, cost and organic traffic)
  24,161,392
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  2
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
Full SEMrush Report >>

Revenue report ▼

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

How much would zadzmo.org make?

Daily Revenue:
$10.32
Monthly Revenue:
$309.60
Yearly Revenue:
$3,766.80
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 1,571$7.59
 
Austria 397$0.80
 
Canada 113$0.68
 
United Kingdom 206$0.55
 
Japan 416$0.15

Loss of money due to Adblock?

Daily Revenue Loss:
$1.84
Monthly Revenue Loss:
$55.10
Yearly Revenue Loss:
$670.37
Daily Pageviews Blocked:
459
Monthly Pageviews Blocked:
13,782
Yearly Pageviews Blocked:
167,675

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 283$1.37
 
Austria 103$0.21
 
Canada 28$0.17
 
United Kingdom 33$0.09
 
Japan 12$0.00

How much is zadzmo.org worth?

Website Value:
$11.3K

Ad Experience Report ▼

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

Mobile summary

Root domain:
zadzmo.org
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:
zadzmo.org
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:
zadzmo.org
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 zadzmo.org hosted? ▼

Zadzmo.org may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
2602:f977:800::e076:63ff:fe88:2d24, 166.84.136.36
ASN:
AS2033 
ISP:
Panix Network Information Center 
Server Location:

United States, US
 

Other sites hosted on 166.84.136.36

There are no other sites hosted on this IP

How fast does zadzmo.org load? ▼

The average loading time of zadzmo.org is 63 ms. The Desktop speed index is 100 and mobile speed index is 100.
Average Load Time:
63 ms

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 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)0ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)1.1s 60% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 60% 26% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 26% 13% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 13%
First Contentful Paint (FCP)1.9s 74% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 74% 11% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 11% 14% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 14%
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)31ms 100% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 100% 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.9s 81% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 81% 8% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 8% 9% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 9%

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)0ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)1.1s 60% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 60% 26% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 26% 13% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 13%
First Contentful Paint (FCP)1.9s 74% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 74% 11% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 11% 14% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 14%
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)31ms 100% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 100% 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.9s 81% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 81% 8% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 8% 9% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 9%

Lab Data

First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful 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
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
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Minimize third-party usage  
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact
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
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
Largest Contentful Paint 0.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Third parties  
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
Speed Index 0.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
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
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
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
First Contentful Paint 0.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
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 0.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
Max Potential First Input Delay 20 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 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
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Does not have 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
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

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 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)0ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)1.5s 60% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 48% 31% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 31% 20% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 20%
First Contentful Paint (FCP)2.3s 74% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 70% 10% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 10% 19% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 19%
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)296ms 100% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 7% 92% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 92% 0% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.9s 81% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 72% 7% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 7% 20% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 20%

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)0ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)1.5s 48% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 48% 31% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 31% 20% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 20%
First Contentful Paint (FCP)2.3s 70% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 70% 10% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 10% 19% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 19%
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)296ms 7% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 7% 92% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 92% 0% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.9s 72% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 72% 7% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 7% 20% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 20%

Lab Data

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
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
Max Potential First Input Delay 20 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
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
Does not have 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
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
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Largest Contentful Paint 1.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest 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
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
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Speed Index 2.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
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
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
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
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Minimize third-party usage  
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact
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
Third parties  
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code

Does zadzmo.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 zadzmo.org are reduced by %.
zadzmo.org does not use compression.
Original size: 894 B
Compressed size: n/a
File reduced by: (%)

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. zadzmo.org has 70 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  70
Safety Confidence:
  13

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. zadzmo.org supports HTTPS.
 zadzmo.org supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: zadzmo.org
Organization:
Location:
Issuer: R10
Valid from: Jan 30 04:25:59 2025 GMT
Valid until: Apr 30 04:25:58 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R10
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: 2048 Bits
Common Name: Let's Encrypt Authority X3
Organization: Let's Encrypt
Location: US
Issuer: DST Root CA X3
Valid from: Mar 17 16:40:46 2016 GMT
Valid until: Mar 17 16:40:46 2021 GMT
Authority: CA:TRUE
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.
 zadzmo.org does not support 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: Tue, 25 Mar 2025 06:30:01 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: keep-alive
X-Clacks-Overhead: GNU Terry Pratchett
Strict-Transport-Security: max-age=31536000; includeSubDomains

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
MX ack.zs-zero.net 300
TXT v=TLSRPTv1; rua=mailto:dmarc@zadzmo.org 300
TXT v=spf1 mx -all 300
SOA 300
Mname syn.zs-zero.net
Rname sys.zadzmo.org
Serial Number 2025031701
Refresh 10800
Retry 3600
Expire 604800
Minimum TTL 3600
AAAA 2602:f977:800::e076:63ff:fe88:2d24 256
A 166.84.136.36 256
NS ns2.access.net 300
NS ns1.access.net 300
NS ack.zs-zero.net 300
NS syn.zs-zero.net 300
CAA letsencrypt.org 300
CAA ; 300

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 December 10, 2004 and will expire on December 10, 2025 if not renewed. This website is now assigned through the registrar GKG.NET, INC.. The WHOIS data for this website's domain was last updated on June 15, 2023.
Domain Created:
2004-12-10
Domain Expires:
2025-12-10
Domain Updated:
2023-06-15
Domain Age:
20 years 6 months 13 days
Domain Registrar:
GKG.NET, INC.
Domain Owner:
n/a
WhoIs:
 

Domain Name: ZADZMO.ORG
Registry Domain ID: D105321312-LROR
Registrar WHOIS Server: whois.gkg.net
Registrar URL: http://www.gkg.net
Updated Date: 2023-06-15T07:30:48.0Z
Creation Date: 2004-12-10T15:26:53.0Z
Registrar Registration Expiration Date: 2025-12-10T15:26:53.0Z
Registrar: GKG.NET, INC.
Registrar IANA ID: 93
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.8776951790
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registrant Organization: n/a
Registrant State/Province: KY
Registrant Country: US
Registrant Email: https://www.gkg.net/apps/contact-domain/zadzmo.org
Admin Email: https://www.gkg.net/apps/contact-domain/zadzmo.org
Tech Email: https://www.gkg.net/apps/contact-domain/zadzmo.org
Name Server: SYN.ZS-ZERO.NET
Name Server: NS1.ACCESS.NET
Name Server: NS2.ACCESS.NET
Name Server: ACK.ZS-ZERO.NET
DNSSEC: signedDelegation
URL of the ICANN WHOIS Data Problem Reporting System:  http://wdprs.internic.net/
>>> Last update of WHOIS database: 2025-03-25T01:30:45.0Z