Pulse.aws
Pulse
Domain Summary
What is the traffic rank for Pulse.aws?
• Pulse.aws ranks #2,438,106 globally on HypeStat.
What percent of global Internet users visit Pulse.aws?
• 4.76E-5% of global Internet users visit Pulse.aws
How many people visit Pulse.aws each day?
• Pulse.aws receives approximately 2.3K visitors and 5,352 page impressions per day.
Which countries does Pulse.aws receive most of its visitors from?
• Pulse.aws is mostly visited by people located in United States,India,Korea, Republic of.
How much Pulse.aws can earn?
• Pulse.aws should earn about $11.88/day from advertising revenue.
What is Pulse.aws estimated value?
• Estimated value of Pulse.aws is $10,280.14.
What IP addresses does Pulse.aws resolve to?
• Pulse.aws resolves to the IP addresses 18.160.181.94.
Where are Pulse.aws servers located in?
• Pulse.aws has servers located in United States.
pulse.aws Profile
What technologies does pulse.aws use?
These are the technologies used at pulse.aws. pulse.aws has a total of 5 technologies installed in 4 different categories.
pulse.aws Traffic Analysis
Pulse.aws is ranked #2,438,106 in the world. This website is viewed by an estimated 2.3K visitors daily, generating a total of 5.4K pageviews. This equates to about 71K monthly visitors. Pulse.aws traffic has increased by 49.47% compared to last month.Daily Visitors2.3K
71.58%
Monthly Visits71K
49.47%
Pages per Visit2.28
59.42%
Visit duration01:55
74.5%
Bounce Rate41.20%
83.42%
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- 2,344
- Monthly Visits:
- 71,023
- Pages per Visit:
- 2.28
- Daily Pageviews:
- 5,352
- Avg. visit duration:
- 01:55
- Bounce rate:
- 41.20%
- Global Reach:
- 4.76E-5%
- Monthly Visits (SEMrush):
- 66,937
- Monthly Unique Visitors (SEMrush):
- 45,609
- Monthly Visits (SimilarWeb):
- 71,767
- HypeRank:
- 2,438,106
- SEMrush Rank:
- 13,549,665
- SimilarWeb Rank:
- 461,031
Traffic sources
- Direct:
- 79.43%
- Referral:
- 13.65%
- Search:
- 5.88%
- Social:
- 1.04%
- Paid:
- 0%
Desktop vs Mobile
- Desktop:
- 55.99%
- Mobile:
- 44.01%
Total Visits Last 3 Months
59.4K
FEB
47.5K
MAR
71K
APR
Visitors by country
- Country
- Users%
- United States 21.94%
- India 20.74%
- Korea, Republic of 14.62%
- Japan 12.80%
- Brazil 9.91%
Which sites are competitors to pulse.aws?
Websites similar to pulse.aws 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.- Domain
- CompareDaily Visitors
- chatgpt.com
- Compare >203.5M
- github.com
- Compare >15.9M
Last update was 212 days ago
This can take up to 60 seconds. Please wait...
This can take up to 60 seconds. Please wait...
*HypeStat.com is not promoting or affiliated with pulse.aws 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.- Domain:
- pulse.aws
- Rank:
(Rank based on keywords, cost and organic traffic) - 13,549,665
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 35
- 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
Revenue report ▼
Google.com would generate approximately $11.9 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $356.4 and annual gross revenue of approximately $4.3K. Based on these figures, the site's net worth is estimated at around $10.3K.How much would pulse.aws make?
- Daily Revenue:
- $11.88
- Monthly Revenue:
- $356.40
- Yearly Revenue:
- $4,336.20
Daily earning by country
- CountryPageviewsEarning
- United States 1,174$5.67
- Brazil 530$0.71
- Korea, Republic of 782$0.47
- India 1,110$0.42
- Japan 685$0.25
Loss of money due to Adblock?
- Daily Revenue Loss:
- $1.21
- Monthly Revenue Loss:
- $36.23
- Yearly Revenue Loss:
- $440.75
- Daily Pageviews Blocked:
- 606
- Monthly Pageviews Blocked:
- 18,176
- Yearly Pageviews Blocked:
- 221,137
Daily revenue loss by country
- CountryBlockedLost Money
- United States 211$1.02
- India 311$0.12
- Brazil 32$0.04
- Korea, Republic of 31$0.02
- Japan 21$0.01
How much is pulse.aws worth?
- Website Value:
- $10.3K
Ad Experience Report ▼
Summary of the ad experience rating of a website for a specific platform.Mobile summary
- Root domain:
- pulse.aws
- 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:
- pulse.aws
- 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:
- pulse.aws
- 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 pulse.aws hosted? ▼
Pulse.aws may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.- Server IP:
- 18.160.181.94
- ASN:
- AS16509
- ISP:
- Amazon.com, Inc.
- Server Location:
United States, US
Other sites hosted on 18.160.181.94
How fast does pulse.aws load? ▼
The average loading time of pulse.aws is 145 ms. The Desktop speed index is 57 and mobile speed index is 48.- Average Load Time:
- 145 ms
Page Speed (Google PageSpeed Insights) - Desktop
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)3ms
Time To First Byte (TTFB)1.4s
First Contentful Paint (FCP)5.1s
First Input Delay (FID)0
Interaction To Next Paint (INP)95ms
Largest Contentful Paint (LCP)6.5s
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)3ms
Time To First Byte (TTFB)1.4s
First Contentful Paint (FCP)5.1s
First Input Delay (FID)0
Interaction To Next Paint (INP)95ms
Largest Contentful Paint (LCP)6.5s
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
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
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
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
Use efficient cache lifetimes
A long cache lifetime can speed up repeat visits to your page. Learn more
A long cache lifetime can speed up repeat visits to your page. Learn more
3rd parties
3rd party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of 3rd party code
3rd party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of 3rd party code
Legacy JavaScript
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
Total Blocking Time 280 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
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
INP by phase
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
First Contentful Paint 2.4 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 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
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
LCP request discovery
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
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
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
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
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
Duplicated JavaScript
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Largest Contentful Paint 2.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
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Time to Interactive 2.8 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
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
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
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
Max Potential First Input Delay 330 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
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 Meaningful Paint
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Speed Index 3.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.
Cumulative Layout Shift (CLS)2ms
Time To First Byte (TTFB)1.8s
First Contentful Paint (FCP)6.7s
First Input Delay (FID)0
Interactive To Next Paint (INP)251ms
Largest Contentful Paint (LCP)8.3s
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)2ms
Time To First Byte (TTFB)1.8s
First Contentful Paint (FCP)6.7s
First Input Delay (FID)0
Interactive To Next Paint (INP)251ms
Largest Contentful Paint (LCP)8.3s
Lab Data
First Contentful Paint 14.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 Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint 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
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
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
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
Duplicated JavaScript
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
First Meaningful Paint
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Legacy JavaScript
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
Largest Contentful Paint 15.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
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time 320 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
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
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
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
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
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
LCP request discovery
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
INP by phase
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Speed Index 14.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Time to Interactive 15.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
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
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 370 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
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
Use efficient cache lifetimes
A long cache lifetime can speed up repeat visits to your page. Learn more
A long cache lifetime can speed up repeat visits to your page. Learn more
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
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
3rd parties
3rd party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of 3rd party code
3rd party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of 3rd party code
Does pulse.aws 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 pulse.aws are reduced by %.
pulse.aws does not use compression.
Original size: 887 B
Compressed size: n/a
File reduced by: (%)
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.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. pulse.aws supports HTTPS. pulse.aws supports HTTPS
Verifying SSL Support. Please wait...
Common Name: pulse.aws
Organization:
Location:
Issuer: Amazon RSA 2048 M02
Valid from: May 21 00:00:00 2025 GMT
Valid until: Jun 19 23:59:59 2026 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Organization:
Location:
Issuer: Amazon RSA 2048 M02
Valid from: May 21 00:00:00 2025 GMT
Valid until: Jun 19 23:59:59 2026 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: Amazon RSA 2048 M02
Organization: Amazon
Location: US
Issuer: Amazon Root CA 1
Valid from: Aug 23 22:25:30 2022 GMT
Valid until: Aug 23 22:25:30 2030 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Organization: Amazon
Location: US
Issuer: Amazon Root CA 1
Valid from: Aug 23 22:25:30 2022 GMT
Valid until: Aug 23 22:25:30 2030 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: Amazon Root CA 1
Organization: Amazon
Location: US
Issuer: Starfield Services Root Certificate Authority - G2
Valid from: May 25 12:00:00 2015 GMT
Valid until: Dec 31 01:00:00 2037 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Organization: Amazon
Location: US
Issuer: Starfield Services Root Certificate Authority - G2
Valid from: May 25 12:00:00 2015 GMT
Valid until: Dec 31 01:00:00 2037 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. pulse.aws 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.content-type: text/html
content-length: 887
x-amz-id-2: 3xe5Xxw9u68wy5wHFazHPztXNeyVYjEGY3QqFWH9CTSn6IdK6hQXNdf4YBXSTLehEZmoGYnfWOQ=
x-amz-request-id: Q3JHB381SF725A7G
date: Fri, 23 May 2025 11:57:24 GMT
last-modified: Fri, 23 May 2025 06:00:10 GMT
etag: "a48338c56598a543925ee55221dd688b"
x-amz-server-side-encryption: AES256
x-amz-version-id: APlF1jTgYF7jOGYYRtvFkhNBzgiGyaHJ
accept-ranges: bytes
server: AmazonS3
x-cache: Miss from cloudfront
via: 1.1 7cc224be3664680df186a12039cdc424.cloudfront.net (CloudFront)
x-amz-cf-pop: MSP50-P2
x-amz-cf-id: bBP_fLZlL89gmFSdNaA_bf4ugEZLaUT11NoMyeBQ5n6nCVU4eXkdyA==
x-frame-options: DENY
content-security-policy: default-src 'none'; font-src 'self'; style-src 'self' 'unsafe-inline'; connect-src 'self' https://*.pulse.aws/ https://*.pulse.amazon/ https://*.community.buildon.aws/ https://*.s3.amazonaws.com/ https://*.s3.*.amazonaws.com/ https://*.s3.us-east-1.amazonaws.com/ https://*.execute-api.*.amazonaws.com/ https://dataplane.rum.us-east-1.amazonaws.com https://cognito-identity.us-east-1.amazonaws.com https://sts.us-east-1.amazonaws.com/ https://api-v2.builderprofile.aws.dev https://token.builderprofile.aws.dev https://gamma-api-v2.builderprofile.aws.dev https://gamma-token.builderprofile.aws.dev https://prod.log.shortbread.aws.dev https://prod.tools.shortbread.aws.dev; script-src 'self' https://gamma-cdn.builderprofile.aws.dev/bp.min.js https://cdn.builderprofile.aws.dev/bp.min.js https://widget.pulse.aws.dev; img-src 'self' blob: https://*.pulse.aws/ https://*.pulse.amazon/ https://*.awsstatic.com/ https://*.builderprofile.aws.dev/ https://*.media-amazon.com/ https://amazonmr.au1.qualtrics.com https://avatars.githubusercontent.com https://aws.amazon.com https://bit.ly https://cdn.concepts.co.nz https://d12jloqbpngwzw.cloudfront.net https://d1v7v25n68zbot.cloudfront.net https://d2kpsbq6upjz7l.cloudfront.net https://d2o976o96898gx.cloudfront.net https://dcbv9rjz4cun6.cloudfront.net/ https://drive.google.com https://fixthechaos.com https://github.com https://i.imgur.com https://images.ctfassets.net https://internal-cdn.amazon.com/ https://jfe-cdn.qualtrics.com https://lh3.googleusercontent.com https://marvel-b1-cdn.bc0a.com https://s3-us-west-2.amazonaws.com https://upload.wikimedia.org https://web-bucket-jay-230404.s3.ap-northeast-2.amazonaws.com; object-src 'none'; frame-ancestors 'none'; base-uri 'self'; upgrade-insecure-requests
x-content-type-options: nosniff
strict-transport-security: max-age=47304000; includeSubDomains
cache-control: no-store, no-cache
cross-origin-opener-policy: same-origin
pragma: no-cache
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 |
| SOA | 900 | ||
| Mname | ns-754.awsdns-30.net | ||
| Rname | awsdns-hostmaster.amazon.com | ||
| Serial Number | 1 | ||
| Refresh | 7200 | ||
| Retry | 900 | ||
| Expire | 1209600 | ||
| Minimum TTL | 86400 | ||
| A | 18.160.181.59 | 16 | |
| A | 18.160.181.31 | 16 | |
| A | 18.160.181.127 | 16 | |
| A | 18.160.181.94 | 16 | |
| NS | 172610 | ||
| NS | 172610 | ||
| NS | 172610 | ||
| NS | 172610 |