pdax.ph Pdax.ph

   
PDAX | Cryptocurrency Trading Platform in the Philippines

Domain Summary

What is the traffic rank for Pdax.ph?

• Pdax.ph ranks #3,172,924 globally on HypeStat.

What percent of global Internet users visit Pdax.ph?

• 2.95E-5% of global Internet users visit Pdax.ph

How many people visit Pdax.ph each day?

• Pdax.ph receives approximately 1.5K visitors and 11,053 page impressions per day.

Which countries does Pdax.ph receive most of its visitors from?

• Pdax.ph is mostly visited by people located in Philippines,United Kingdom,Thailand.

How much Pdax.ph can earn?

• Pdax.ph should earn about $14.32/day from advertising revenue.

What is Pdax.ph estimated value?

• Estimated value of Pdax.ph is $14,142.14.

What IP addresses does Pdax.ph resolve to?

• Pdax.ph resolves to the IP addresses 192.0.78.177.

Where are Pdax.ph servers located in?

• Pdax.ph has servers located in San Francisco, California, 94110, United States.

pdax.ph Profile

Title:PDAX | Cryptocurrency Trading Platform in the Philippines Description:Buy, sell, and trade the world’s top cryptocurrencies at competitive market rates. %
Category:Games / Video Games Consoles and Accessories
Edit Site Info

What technologies does pdax.ph use?

These are the technologies used at pdax.ph. pdax.ph has a total of 18 technologies installed in 17 different categories.
UI frameworks
Bootstrap Bootstrap
WordPress plugins
Contact Form 7 Contact Form 7
Gutenberg Gutenberg
Yoast SEO Yoast SEO
Analytics
Google Analytics Google Analytics
Editors
Gutenberg Gutenberg
Security
HSTS HSTS
Miscellaneous
HTTP/3 HTTP/3
Open Graph Open Graph
JavaScript Libraries
jQuery jQuery
jQuery Migrate jQuery Migrate
Swiper Swiper
Web Servers
Nginx Nginx
Reverse proxies
Nginx Nginx
Widgets
OWL Carousel OWL Carousel
Font Scripts
Typekit Typekit
CMS
WordPress WordPress
Blogs
WordPress WordPress
PaaS
WordPress.com WordPress.com
SEO
Yoast SEO Yoast SEO
Programming Languages
PHP PHP
Databases
MySQL MySQL

pdax.ph Traffic Analysis

Pdax.ph is ranked #3,172,924 in the world. This website is viewed by an estimated 1.5K visitors daily, generating a total of 11.1K pageviews. This equates to about 44.1K monthly visitors. Pdax.ph traffic has decreased by 39.4% compared to last month.
Daily Visitors1.5K
5.68%
Monthly Visits44.1K
39.4%
Pages per Visit7.60
19.54%
Visit duration06:30
54.64%
Bounce Rate34.44%
57.95%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
1,455
Monthly Visits:
44,087
Pages per Visit:
7.60
Daily Pageviews:
11,053
Avg. visit duration:
06:30
Bounce rate:
34.44%
Global Reach:
2.95E-5%
Monthly Visits (SEMrush):
29,418
Monthly Unique Visitors (SEMrush):
23,369
Monthly Visits (SimilarWeb):
44,081
HypeRank:
3,172,924
SEMrush Rank:
2,428,653
SimilarWeb Rank:
484,132
*All traffic values are estimates only.

Traffic sources

Direct:
87.07%
Referral:
3.94%
Search:
8.35%
Social:
0.64%
Paid:
0%

Desktop vs Mobile

Desktop:
29.29%
Mobile:
70.71%

Total Visits Last 3 Months

81.6K
DEC
72.8K
JAN
44.1K
FEB

Visitors by country

Country
Users%
 
Philippines 59.30%
 
United Kingdom 15.65%
 
Thailand 3.70%
 
China 3.67%
 
United States 3.30%

Where do visitors go on pdax.ph?

 
Reach%Pageviews%PerUser
trade.pdax.ph
91.85%79.08%3.8
pdax.ph
51.01%11.56%1.0
payments.pdax.ph
10.67%3.20%1.3
support.pdax.ph
8.45%4.46%2.3
kyc.pdax.ph
6.08%1.38%1

Which sites are competitors to pdax.ph?

Websites similar to pdax.ph 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 82 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with pdax.ph 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:
387
Bing Index:
1,350

  ▼

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:
  pdax.ph
Rank:
(Rank based on keywords, cost and organic traffic)
  2,428,653
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  284
Organic Traffic:
(Number of visitors coming from top 20 search results)
  235
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $1,562.00
Full SEMrush Report >>

Revenue report ▼

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

How much would pdax.ph make?

Daily Revenue:
$14.32
Monthly Revenue:
$429.60
Yearly Revenue:
$5,226.80
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United Kingdom 1,730$4.64
 
United States 364$1.76
 
Philippines 6,555$1.31
 
Thailand 409$0.09
 
China 406$0.04

Loss of money due to Adblock?

Daily Revenue Loss:
$1.16
Monthly Revenue Loss:
$34.82
Yearly Revenue Loss:
$423.59
Daily Pageviews Blocked:
878
Monthly Pageviews Blocked:
26,353
Yearly Pageviews Blocked:
320,630

Daily revenue loss by country

 
CountryBlockedLost Money
 
United Kingdom 277$0.74
 
United States 66$0.32
 
Philippines 459$0.09
 
China 53$0.01
 
Thailand 25$0.01

How much is pdax.ph worth?

Website Value:
$14.1K

Ad Experience Report ▼

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

Mobile summary

Root domain:
pdax.ph
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:
pdax.ph
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:
pdax.ph
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 pdax.ph hosted? ▼

Pdax.ph may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
192.0.78.177
ASN:
AS2635 
ISP:
Automattic, Inc 
Server Location:
San Francisco
California, CA
94110
United States, US
 

Other sites hosted on 192.0.78.177

How fast does pdax.ph load? ▼

The average loading time of pdax.ph is 51 ms. The Desktop speed index is 88 and mobile speed index is 64.
Average Load Time:
51 ms

Page Speed (Google PageSpeed Insights) - Desktop

88
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)20ms 20% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 20% 76% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 76% 2% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 2%
Time To First Byte (TTFB)818ms 74% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 74% 20% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 20% 5% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)1.8s 75% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 75% 15% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 15% 8% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 8%
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)14ms 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)1.9s 85% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 85% 8% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 8% 5% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 5%

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)20ms 19% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 19% 76% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 76% 4% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 4%
Time To First Byte (TTFB)976ms 57% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 57% 36% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 36% 5% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)1.8s 75% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 75% 17% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 17% 7% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 7%
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)17ms 98% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 98% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.1s 82% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 82% 11% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 11% 5% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 5%

Lab Data

Time to Interactive 1.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
Forced reflow  
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
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 about the Total Blocking Time 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
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Preconnect to required origins  
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
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 about the Maximum Potential First Input Delay 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
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
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Largest Contentful Paint 0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric

Page Speed (Google PageSpeed Insights) - Mobile

64
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)5ms 20% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 96% 3% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 3% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)1.6s 74% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 39% 40% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 40% 20% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 20%
First Contentful Paint (FCP)2.6s 75% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 54% 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)127ms 98% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 87% 9% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 9% 3% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 3%
Largest Contentful Paint (LCP)3.3s 85% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 64% 16% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 16% 18% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 18%

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 95% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 95% 4% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 4% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)1.6s 31% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 31% 48% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 48% 19% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 19%
First Contentful Paint (FCP)2.5s 55% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 55% 27% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 27% 16% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 16%
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)120ms 87% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 87% 9% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 9% 3% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 3%
Largest Contentful Paint (LCP)2.9s 67% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 67% 19% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 19% 13% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 13%

Lab Data

INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
Preconnect to required origins  
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
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 5.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Total Blocking Time 50 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 Contentful Paint 3.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
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
Max Potential First Input Delay 80 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
Time to Interactive 11.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Largest Contentful Paint 11.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
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Optimize DOM size  
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size
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

Does pdax.ph 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 pdax.ph are reduced by 81%.
pdax.ph use br compression.
Original size: 130.96 KB
Compressed size: 23.85 KB
File reduced by: 107.11 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. pdax.ph supports HTTPS.
 pdax.ph supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: tls.automattic.com
Organization:
Location:
Issuer: E5
Valid from: Feb 27 01:24:25 2025 GMT
Valid until: May 28 01:24:24 2025 GMT
Authority: CA:FALSE
Keysize:
Common Name: E5
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 GMT
Authority: CA:TRUE
Keysize:

Verify HTTP/2 Support ▼

HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency.
 pdax.ph supports HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

Http Header ▼

HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server. 
server: nginx
date: Wed, 26 Mar 2025 07:33:52 GMT
content-type: text/html; charset=UTF-8
strict-transport-security: max-age=31536000
vary: Accept-Encoding
last-modified: Wed, 26 Mar 2025 07:31:13 GMT
cache-control: max-age=142, must-revalidate
x-nananana: Batcache-Hit
x-hacker: Want root?  Visit join.a8c.com and mention this header.
host-header: WordPress.com
vary: accept, content-type, cookie
link: <https://pdax.ph/wp-json/>; rel="https://api.w.org/"
link: <https://wp.me/fHjcT>; rel=shortlink
content-encoding: br
x-ac: 2.mdw _atomic_dca BYPASS
alt-svc: h3=":443"; ma=86400

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 google-site-verification=BaqVCn7i7rOdhe7T0fAiXsmPO7qQ3EmTjCapG9Eh_Iw 600
TXT S6B149TYVAAL86ABFCAHGIXSKTE01KNELUXTVM9K 600
TXT atlassian-domain-verification=dbWSXOYxZc7JNfVbVfzz8o4bFB7Y1KcVF4cLD3cmoU6qdQUUaQ1fj1HqCtbaPzbx 600
TXT include:_spf.atlassian.net 600
TXT 00d2x0000032v9meaq 600
TXT google-site-verification=pWDkQ954m2iQxdyEuaHQPJIvCwelK3TPsPawRjEIiqQ 600
TXT spycloud-domain-verification=acdad98d-13bb-4361-b37b-76a6c47dd340 600
TXT google-site-verification=CxR3MYIr634PQjnFLXEe1hnM9wZYQ6HC9dtlYL-Nmi0 600
TXT google-site-verification=z31ECHzxcloPTtxZssg0FoNgtTmkkQsqYKMP6GOhhyU 600
TXT google-site-verification=Bhfc6_04iSoJp3Q1S0qntCxjcaO4BtwOisRUhHB83V0 600
TXT atlassian-sending-domain-verification=b114e254-94e6-48d2-8659-9f33290c6d51 600
TXT v=spf1 include:_spf.google.com include:amazonses.com include:spf.tmes.trendmicro.com include:_spf.phishinsight.com include:mail.zendesk.com include:sendgrid.net ~all 600
MX alt3.aspmx.l.google.com 600
MX alt4.aspmx.l.google.com 600
MX alt2.aspmx.l.google.com 600
MX pdax.in.tmes.trendmicro.com 600
MX aspmx.l.google.com 600
MX alt1.aspmx.l.google.com 600
SOA 900
Mname ns-245.awsdns-30.com
Rname awsdns-hostmaster.amazon.com
Serial Number 1
Refresh 7200
Retry 900
Expire 1209600
Minimum TTL 86400
A 192.0.78.215 115
A 192.0.78.177 115
NS ns-1872.awsdns-42.co.uk 86215
NS ns-245.awsdns-30.com 86215
NS ns-667.awsdns-19.net 86215
NS ns-1513.awsdns-61.org 86215
CAA amazon.com 300
CAA amazontrust.com 300
CAA letsencrypt.org 300
CAA amazonaws.com 300
CAA digicert.com 300
CAA awstrust.com 300
CAA entrust.net 300
CAA amazon.com 300
CAA pki.goog 300