animepahe.ru Animepahe.ru

   
DDoS-Guard

Domain Summary

What is the traffic rank for Animepahe.ru?

• Animepahe.ru ranks #2,421 globally on HypeStat.

What percent of global Internet users visit Animepahe.ru?

• 0.0161167% of global Internet users visit Animepahe.ru

How many people visit Animepahe.ru each day?

• Animepahe.ru receives approximately 794.5K visitors and 5,646,440 page impressions per day.

Which countries does Animepahe.ru receive most of its visitors from?

• Animepahe.ru is mostly visited by people located in United States,Philippines,India.

How much Animepahe.ru can earn?

• Animepahe.ru should earn about $18,572.33/day from advertising revenue.

What is Animepahe.ru estimated value?

• Estimated value of Animepahe.ru is $20,186,253.07.

What IP addresses does Animepahe.ru resolve to?

• Animepahe.ru resolves to the IP addresses 185.178.208.138.

Where are Animepahe.ru servers located in?

• Animepahe.ru has servers located in Russia.

animepahe.ru Profile

Title:DDoS-Guard
Description:Watch or download anime shows in HD 720p/1080p.
Tags:
hd
720p
hardsub
mp4
anime
english
subtitle
pahe
mini
Category:Games / Video Games Consoles and Accessories
About: Animepahe.ru is an online streaming website dedicated to providing users with access to a wide selection of anime series and movies. The website offers free and premium services, with the free version allowing users to stream content in SD quality, while the premium version offers access to HD quality streaming. The website also has an extensive library of manga, as well as a forum and chatroom for users to discuss their favorite anime and manga.
*This text is generated by artificial intelligence and may not be accurate. Edit Site Info

What technologies does animepahe.ru use?

These are the technologies used at animepahe.ru. animepahe.ru has a total of 8 technologies installed in 8 different categories.
UI frameworks
Bootstrap Bootstrap
CDN
CloudFlare CloudFlare
Analytics
Cloudflare Browser Insights Cloudflare Browser Insights
RUM
Cloudflare Browser Insights Cloudflare Browser Insights
Security
HSTS HSTS
Miscellaneous
HTTP/3 HTTP/3
Open Graph Open Graph
Web Frameworks
Laravel Laravel
Programming Languages
PHP PHP

animepahe.ru Traffic Analysis

Animepahe.ru is ranked #2,421 in the world. This website is viewed by an estimated 794.5K visitors daily, generating a total of 5.6M pageviews. This equates to about 24.1M monthly visitors. Animepahe.ru traffic has decreased by 14.92% compared to last month.
Daily Visitors794.5K
5.89%
Monthly Visits24.1M
14.92%
Pages per Visit7.11
5.37%
Visit duration08:48
0.99%
Bounce Rate27.05%
3.41%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
794,539
Monthly Visits:
24,074,532
Pages per Visit:
7.11
Daily Pageviews:
5,646,440
Avg. visit duration:
08:48
Bounce rate:
27.05%
Global Reach:
0.0161167%
Monthly Visits (SEMrush):
108,845,634
Monthly Unique Visitors (SEMrush):
9,699,275
Monthly Visits (SimilarWeb):
24,076,950
HypeRank:
2,421
SEMrush Rank:
21,225
SimilarWeb Rank:
1,857
*All traffic values are estimates only.

Traffic sources

Direct:
95.70%
Referral:
0.82%
Search:
3.10%
Social:
0.37%
Paid:
0.01%

Desktop vs Mobile

Desktop:
16.00%
Mobile:
84.00%

Total Visits Last 3 Months

25.2M
DEC
28.3M
JAN
24.1M
FEB

Visitors by country

Country
Users%
 
United States 29.99%
 
Philippines 11.79%
 
India 9.78%
 
United Kingdom 6.06%
 
Nigeria 3.60%

Where do visitors go on animepahe.ru?

 
Reach%Pageviews%PerUser
animepahe.ru
100.00%100.00%1.0

Which sites are competitors to animepahe.ru?

Websites similar to animepahe.ru 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 37 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with animepahe.ru 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:
6
Bing Index:
21,800

  ▼

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:
  animepahe.ru
Rank:
(Rank based on keywords, cost and organic traffic)
  21,225
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  10,780
Organic Traffic:
(Number of visitors coming from top 20 search results)
  107,673
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $82,579.00
Full SEMrush Report >>

Revenue report ▼

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

How much would animepahe.ru make?

Daily Revenue:
$18,572.33
Monthly Revenue:
$557,169.90
Yearly Revenue:
$6,778,900.45
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 1,693,198$8,178.15
 
United Kingdom 342,341$917.47
 
India 552,376$209.90
 
Nigeria 203,346$201.31
 
Philippines 665,886$133.18

Loss of money due to Adblock?

Daily Revenue Loss:
$1,690.98
Monthly Revenue Loss:
$50,729.51
Yearly Revenue Loss:
$617,209.02
Daily Pageviews Blocked:
564,894
Monthly Pageviews Blocked:
16,946,833
Yearly Pageviews Blocked:
206,186,473

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 304,776$1,472.07
 
United Kingdom 54,775$146.80
 
India 154,665$58.77
 
Philippines 46,612$9.32
 
Nigeria 4,067$4.03

How much is animepahe.ru worth?

Website Value:
$20.2M

Ad Experience Report ▼

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

Mobile summary

Root domain:
animepahe.ru
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:
animepahe.ru
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:
animepahe.ru
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 animepahe.ru hosted? ▼

Animepahe.ru may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
185.178.208.138
ASN:
AS57724 
ISP:
Ddos-guard Ltd 
Server Location:

Russia, RU
 

Other sites hosted on 185.178.208.138

How fast does animepahe.ru load? ▼

The average loading time of animepahe.ru is 112 ms. The Desktop speed index is 100 and mobile speed index is 73.
Average Load Time:
112 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 FAST 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 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)675ms 80% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 80% 13% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 13% 5% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)1.0s 88% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 88% 6% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 6% 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)39ms 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% 1% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 1%
Largest Contentful Paint (LCP)2.3s 79% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 79% 12% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 12% 8% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 8%

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)5ms 89% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 89% 10% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 10% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)532ms 86% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 86% 9% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 9% 3% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 3%
First Contentful Paint (FCP)796ms 93% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 93% 3% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 3% 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%
Interaction To Next Paint (INP)59ms 95% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 95% 2% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 2% 1% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.3s 90% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 90% 5% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 5% 4% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 4%

Lab Data

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
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
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
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 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
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
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
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
Third parties  
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Time to Interactive 0.3 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
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
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
Largest Contentful Paint 0.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
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
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
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

73
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)980ms 80% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 67% 20% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 20% 11% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 11%
First Contentful Paint (FCP)1.5s 88% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 80% 10% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 10% 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)158ms 97% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 84% 11% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 11% 3% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 3%
Largest Contentful Paint (LCP)2.7s 79% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 71% 16% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 16% 12% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 12%

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 85% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 85% 7% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 7% 6% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 6%
Time To First Byte (TTFB)625ms 81% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 81% 12% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 12% 6% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 6%
First Contentful Paint (FCP)1.0s 88% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 88% 6% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 6% 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%
Interactive To Next Paint (INP)319ms 67% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 67% 11% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 11% 21% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 21%
Largest Contentful Paint (LCP)1.5s 86% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 86% 6% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 6% 6% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 6%

Lab Data

First Contentful Paint 2.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Max Potential First Input Delay 690 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
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
Total Blocking Time 500 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
Speed Index 2.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
Largest Contentful Paint 3.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint 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
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
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
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful 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 3.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
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
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
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 animepahe.ru 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 animepahe.ru are reduced by -119%.
animepahe.ru use gzip compression.
Original size: 898 B
Compressed size: 1.91 KB
File reduced by: 1.04 KB (-119%)

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. animepahe.ru has 80 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  80
Safety Confidence:
  51

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. animepahe.ru supports HTTPS.
 animepahe.ru supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: animepahe.ru
Organization:
Location:
Issuer: R11
Valid from: Mar 4 02:12:54 2025 GMT
Valid until: Jun 2 02:12:53 2025 GMT
Authority: CA:FALSE
Keysize: 2048
Common Name: R11
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

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.
 animepahe.ru 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: ddos-guard
date: Sun, 23 Mar 2025 15:04:09 GMT
set-cookie: __ddg8_=CFQhjkaPz7m2McUZ; Domain=.animepahe.ru; Path=/; Expires=Sun, 23-Mar-2025 15:24:09 GMT
set-cookie: __ddg10_=1742742249; Domain=.animepahe.ru; Path=/; Expires=Sun, 23-Mar-2025 15:24:09 GMT
set-cookie: __ddg9_=108.178.0.234; Domain=.animepahe.ru; Path=/; Expires=Sun, 23-Mar-2025 15:24:09 GMT
strict-transport-security: max-age=31536000
content-security-policy: upgrade-insecure-requests;
set-cookie: __ddgid_=Waei3x9KFbwWtuIp; Domain=.animepahe.ru; HttpOnly; Path=/; Expires=Mon, 23-Mar-2026 15:04:09 GMT
set-cookie: __ddgmark_=fVz0UyfZEeC574hQ; Domain=.animepahe.ru; HttpOnly; Path=/; Expires=Mon, 24-Mar-2025 15:04:09 GMT
cache-control: no-cache, no-store, must-revalidate
content-type: text/html; charset=UTF-8
content-length: 898

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
A 185.178.208.138 255
NS alberto.ns.cloudflare.com 345555
NS monroe.ns.cloudflare.com 345555
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 March 18, 2019 and will expire on March 18, 2026 if not renewed. This website is now assigned through the registrar ARDIS-RU. The WHOIS data for this website's domain was last updated on April 30, 2025.
Domain Created:
2019-03-18
Domain Expires:
2026-03-18
Domain Age:
6 years 1 months 12 days
Domain Registrar:
ARDIS-RU
WhoIs:
 

% TCI Whois Service. Terms of use:
% https://tcinet.ru/documents/whois_ru_rf.pdf (in Russian)
% https://tcinet.ru/documents/whois_su.pdf (in Russian)

domain:        ANIMEPAHE.RU
nserver:       alberto.ns.cloudflare.com.
nserver:       monroe.ns.cloudflare.com.
state:         REGISTERED, DELEGATED, UNVERIFIED
person:        Private Person
registrar:     ARDIS-RU
admin-contact: https://ardis.ru/whoisfb/animepahe.ru
created:       2019-03-18T13:53:08Z
paid-till:     2026-03-18T13:53:08Z
free-date:     2026-04-18
source:        TCI

Last updated on 2025-03-23T15:03:01Z