24pdd.kz 24pdd.kz

   
ПДД РК 2025 - Правила дорожного движения Республики Казахстан

Domain Summary

What is the traffic rank for 24pdd.kz?

• 24pdd.kz ranks #494,030 globally on HypeStat.

What percent of global Internet users visit 24pdd.kz?

• 4.79E-5% of global Internet users visit 24pdd.kz

How many people visit 24pdd.kz each day?

• 24pdd.kz receives approximately 2.4K visitors and 5,483 page impressions per day.

Which countries does 24pdd.kz receive most of its visitors from?

• 24pdd.kz is mostly visited by people located in Kazakhstan,Russian Federation,Germany.

How much 24pdd.kz can earn?

• 24pdd.kz should earn about $2.05/day from advertising revenue.

What is 24pdd.kz estimated value?

• Estimated value of 24pdd.kz is $2,013.68.

What IP addresses does 24pdd.kz resolve to?

• 24pdd.kz resolves to the IP addresses 2606:4700:3037::ac43:ab2b, 104.21.39.181.

24pdd.kz Profile

Title:ПДД РК 2025 - Правила дорожного движения Республики Казахстан
Description:ПДД РК 2025, Правила дорожного движения Республики Казахстан полностью соответствует официальным в редакции от 13 ноября 2014 года № 1196
Edit Site Info

What technologies does 24pdd.kz use?

These are the technologies used at 24pdd.kz. 24pdd.kz has a total of 12 technologies installed in 14 different categories.
CDN
CloudFlare CloudFlare
Advertising
Google AdSense Google AdSense
Analytics
Google Analytics Google Analytics
Tag Managers
Google Tag Manager Google Tag Manager
JavaScript Libraries
jQuery jQuery
Miscellaneous
Open Graph Open Graph
Programming Languages
PHP PHP
Performance
Priority Hints Priority Hints
WordPress plugins
RankMath SEO RankMath SEO
SEO
RankMath SEO RankMath SEO
Security
reCAPTCHA reCAPTCHA
CMS
WordPress WordPress
Blogs
WordPress WordPress
Databases
MySQL MySQL

24pdd.kz Traffic Analysis

24pdd.kz is ranked #494,030 in the world. This website is viewed by an estimated 2.4K visitors daily, generating a total of 5.5K pageviews. This equates to about 71.5K monthly visitors. 24pdd.kz traffic has decreased by 37.99% compared to last month.
Daily Visitors2.4K
29.08%
Monthly Visits71.5K
37.99%
Pages per Visit2.32
8.84%
Visit duration04:52
32.87%
Bounce Rate49.90%
6.89%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
2,361
Monthly Visits:
71,538
Pages per Visit:
2.32
Daily Pageviews:
5,483
Avg. visit duration:
04:52
Bounce rate:
49.90%
Global Reach:
4.79E-5%
Monthly Visits (SEMrush):
168,953
Monthly Unique Visitors (SEMrush):
78,815
Monthly Visits (SimilarWeb):
69,438
HypeRank:
494,030
SEMrush Rank:
8,906,464
SimilarWeb Rank:
494,030
*All traffic values are estimates only.

Traffic sources

Direct:
79.99%
Referral:
0%
Search:
20.01%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
10.87%
Mobile:
89.13%

Total Visits Last 3 Months

61.5K
DEC
115.4K
JAN
71.5K
FEB

Visitors by country

Country
Users%
 
Kazakhstan 91.11%
 
Russian Federation 6.03%
 
Germany 2.86%

Which sites are competitors to 24pdd.kz?

Websites similar to 24pdd.kz 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.
Last update was 4 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with 24pdd.kz 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:
614

  ▼

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:
  24pdd.kz
Rank:
(Rank based on keywords, cost and organic traffic)
  8,906,464
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  33
Organic Traffic:
(Number of visitors coming from top 20 search results)
  5
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 $2.1 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $61.5 and annual gross revenue of approximately $748.3. Based on these figures, the site's net worth is estimated at around $2K.

How much would 24pdd.kz make?

Daily Revenue:
$2.05
Monthly Revenue:
$61.50
Yearly Revenue:
$748.25
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Kazakhstan 4,996$1.70
 
Germany 157$0.22
 
Russian Federation 330$0.14

Loss of money due to Adblock?

Daily Revenue Loss:
$0.12
Monthly Revenue Loss:
$3.68
Yearly Revenue Loss:
$44.81
Daily Pageviews Blocked:
215
Monthly Pageviews Blocked:
6,456
Yearly Pageviews Blocked:
78,546

Daily revenue loss by country

 
CountryBlockedLost Money
 
Germany 45$0.06
 
Kazakhstan 150$0.05
 
Russian Federation 20$0.01

How much is 24pdd.kz worth?

Website Value:
$2K

Ad Experience Report ▼

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

Mobile summary

Root domain:
24pdd.kz
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:
24pdd.kz
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:
24pdd.kz
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 24pdd.kz hosted? ▼

24pdd.kz may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.

How fast does 24pdd.kz load? ▼

The average loading time of 24pdd.kz is 962 ms. The Desktop speed index is 100 and mobile speed index is 100.
Average Load Time:
962 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 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)1ms 96% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 96% 2% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 2% 1% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 1%
Time To First Byte (TTFB)1.8s 7% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 7% 65% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 65% 26% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 26%
First Contentful Paint (FCP)2.6s 48% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 48% 33% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 33% 17% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 17%
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)28ms 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% 1% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 1%
Largest Contentful Paint (LCP)2.7s 70% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 70% 19% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 19% 10% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 10%

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)1ms 93% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 93% 4% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 4% 2% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 2%
Time To First Byte (TTFB)2.4s 4% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 4% 55% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 55% 40% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 40%
First Contentful Paint (FCP)2.9s 42% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 42% 35% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 35% 22% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 22%
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)45ms 97% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 97% 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)3.5s 54% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 54% 25% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 25% 19% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 19%

Lab Data

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
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
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
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
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 0.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
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Render blocking requests  
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
Max Potential First Input Delay 40 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
Largest Contentful Paint 0.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
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
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
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 Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric

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 96% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 97% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 1% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 1%
Time To First Byte (TTFB)1.7s 7% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 34% 41% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 41% 23% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 23%
First Contentful Paint (FCP)2.7s 48% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 53% 26% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 26% 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)139ms 98% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 90% 8% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 8% 1% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 1%
Largest Contentful Paint (LCP)2.8s 70% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 69% 20% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 20% 9% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 9%

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)12ms 72% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 72% 8% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 8% 18% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 18%
Time To First Byte (TTFB)1.8s 31% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 31% 43% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 43% 25% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 25%
First Contentful Paint (FCP)2.6s 52% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 52% 28% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 28% 18% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 18%
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)171ms 82% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 82% 15% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 15% 2% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 2%
Largest Contentful Paint (LCP)4.7s 52% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 52% 18% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 18% 29% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 29%

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
Speed Index 2.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
Max Potential First Input Delay 50 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
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
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
Render blocking requests  
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Largest Contentful Paint 1.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
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
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
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
Time to Interactive 1.7 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
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint 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
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

Does 24pdd.kz 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 24pdd.kz are reduced by 81%.
24pdd.kz use br compression.
Original size: 221.11 KB
Compressed size: 41.5 KB
File reduced by: 179.6 KB (81%)

Google Safe Browsing ▼

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

MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites.
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. 24pdd.kz supports HTTPS.
 24pdd.kz supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: 24pdd.kz
Organization:
Location:
Issuer: WE1
Valid from: Feb 11 13:32:05 2025 GMT
Valid until: May 12 14:30:49 2025 GMT
Authority: CA:FALSE
Keysize:
Common Name: WE1
Organization: Google Trust Services
Location: US
Issuer: GTS Root R4
Valid from: Dec 13 09:00:00 2023 GMT
Valid until: Feb 20 14:00:00 2029 GMT
Authority: CA:TRUE
Keysize:
Common Name: GTS Root R4
Organization: Google Trust Services LLC
Location: US
Issuer: GlobalSign Root CA
Valid from: Nov 15 03:43:21 2023 GMT
Valid until: Jan 28 00:00:42 2028 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.
 24pdd.kz 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. 
date: Mon, 24 Mar 2025 22:32:43 GMT
content-type: text/html; charset=UTF-8
x-powered-by: PHP/8.4.1
set-cookie: PHPSESSID=ea372a749c01ab717075f05cd78567d7; path=/; secure; HttpOnly
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
x-dns-prefetch-control: on
link: <https://24pdd.kz/wp-json/>; rel="https://api.w.org/"
link: <https://24pdd.kz/wp-json/wp/v2/pages/7>; rel="alternate"; title="JSON"; type="application/json"
link: <https://24pdd.kz/>; rel=shortlink
x-litespeed-cache-control: public,max-age=604800
x-litespeed-tag: afc_HTTP.200,afc_front,afc_URL.6666cd76f96956469e7be39d750cc7d9,afc_F,afc_Po.7,afc_PGS,afc_guest,afc_,afc_MIN.8c60831d6d0a7979f37e31ac6549efc8.css,afc_MIN.6e8de87fbb3f987e6ffeba84b3ad9c83.js
cf-cache-status: DYNAMIC
vary: accept-encoding
report-to: {"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=59US32YDvjkSp%2FgrqYXUkO2xA34hBYsTe4lv4XAFkPYKxmaJwX52XrKmg1d06lqh7sRqIVpEssDwvDGzQSNj7BB%2FA7BWMFi42z3eTNiwzPZmZ53F1u99iNjD4A%3D%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
speculation-rules: "/cdn-cgi/speculation"
server: cloudflare
cf-ray: 9259a040ed4cf84a-ORD
content-encoding: br
server-timing: cfL4;desc="?proto=TCP&rtt=6883&min_rtt=1544&rtt_var=10806&sent=8&recv=12&lost=0&retrans=0&sent_bytes=3399&recv_bytes=890&delivery_rate=1515436&cwnd=205&unsent_bytes=0&cid=4ae47c1fbccafc68&ts=844&x=0"

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 2606:4700:3037::6815:27b5 236
AAAA 2606:4700:3037::ac43:ab2b 236
A 172.67.171.43 236
A 104.21.39.181 236
NS aiden.ns.cloudflare.com 86336
NS karsyn.ns.cloudflare.com 86336
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 May 31, 2021 and will expire on March 28, 2025 if not renewed. This website is now assigned through the registrar ICPS. The WHOIS data for this website's domain was last updated on October 19, 2024.
Domain Created:
2021-05-31
Domain Updated:
2024-10-19
Domain Age:
3 years 9 months 28 days
Domain Registrar:
ICPS
Domain Owner:
Private Person
WhoIs:
 

Whois Server for the KZ top level domain name.
This server is maintained by KazNIC Organization, a ccTLD manager for Kazakhstan Republic.

Domain Name............: 24pdd.kz

Organization Using Domain Name
Name...................: Turgunali Maraminov
Organization Name......: Private Person
Street Address.........: ul. Universitet, mom 33/8
City...................: Fergana
State..................: Fergana
Postal Code............: 150100
Country................: UZ

Administrative Contact/Agent
NIC Handle.............: PS-KZ-1729318634
Name...................: Turgunali Maraminov
Phone Number...........: +981800516 
Fax Number.............:  
Email Address..........: email

Nameserver in listed order

Primary server.........: aiden.ns.cloudflare.com
Primary ip address.....: 

Secondary server.......: karsyn.ns.cloudflare.com
Secondary ip address...: 162.159.38.194


Domain created: 2021-05-31 13:10:22 (GMT+0:00)
Last modified : 2024-10-19 06:17:14 (GMT+0:00)
Domain status : clientTransferProhibited - 
                clientRenewProhibited - 
                
Registar created: ICPS
Current Registar: ICPS