Skip to content
https://allure.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 2 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.allure.com/
200https://allure.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://allure.com/ → https://www.allure.com/

Consistent

B
TLS Certificate Expiry & Recommendations
213 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

213
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
2 A records, 36 ms lookup
PASS
2 A records, 36 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 166.117.251.134, 52.223.6.210
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:9000:a707:a46c:560f:b721:9702:d75e, 2600:9000:a41b:ef95:eff:32b3:411c:f36c
Info::
4 nameserver(s) configured
Got: ns-836.awsdns-40.net, ns-1935.awsdns-49.co.uk, ns-28.awsdns-03.com, ns-1116.awsdns-11.org
Info::
5 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 36 ms
Got: 36 ms
A166.117.251.134, 52.223.6.210
AAAA2600:9000:a707:a46c:560f:b721:9702:d75e, 2600:9000:a41b:ef95:eff:32b3:411c:f36c
CNAME—
NSns-836.awsdns-40.net, ns-1935.awsdns-49.co.uk, ns-28.awsdns-03.com, ns-1116.awsdns-11.org
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
google-site-verification=986zaA0E28jiRwTMSBJMX9FdaIb9SrmGtnHEjA4uoH8
adobe-idp-site-verification=c2108b9dbc0fc05ff0794006df1c41b6c945bd2c8a904bef754e...
SPF v=spf1 include:_u.allure.com._spf.smart.ondmarc.com -all
atlassian-domain-verification=mYtQWl3namqmk5ikMKT48XVnS+XdjdbkLlkWMcNyvsddK2JDAi...
google-site-verification=OlM1_aRp_v3JYRvB_7xCj5x4JCiKqcBpXxZzQd47Y-Y
google-site-verification=4ajASy4JGdck-_kFHxO_2aKlS8XT8zPQoA9kiknEono
google-site-verification=Uv5GDnzMZbCIftaOtKmNUr3jP-Qj6PGuPvfGLNlf7Sc
google-site-verification=YihYi4950dK8wY1QuLo69gVHoaDZL5WRZE0HvRNMQmc
zapier-domain-verification-challenge=22c91cb2-f338-44fc-82aa-3074404ac405
8ftfly80c5vvknb7t6wzjvw9qyz1p5x8
facebook-domain-verification=8l3yj8s3lp44o5htcw1m2e15q3qenq
google-site-verification=JXANXmFCZGgFOe8n56w4rGpceELNTA2qSGayUsjhXzo
fastly-domain-delegation-readerschoice-208613-2020-27-01
MS=ms45152622
CAALookup not available with standard resolver
Resolved in 36 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 267 ms total
PASS
1 redirect(s), 267 ms total
Info::
Single redirect
Got: https://allure.com → https://www.allure.com/ (301)
Info::
WWW normalization redirect

https://allure.com

118 ms · HTTP/1.1

301

https://www.allure.com/

148 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://allure.com301118 msHTTP/1.1nginx
2https://www.allure.com/200148 msHTTP/1.1CloudFront

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2600:9000:a707:a46c:560f:b721:9702:d75e, 2600:9000:a41b:ef95:eff:32b3:411c:f36c
Got: 1 ms connect
IPv6 Ready
AAAA Records 2600:9000:a707:a46c:560f:b721:9702:d75e, 2600:9000:a41b:ef95:eff:32b3:411c:f36c Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 60 URLs
PASS
robots.txt present, sitemap with 60 URLs
Info::
robots.txt is present
Got: 1879 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 60 entries
Info::
Sitemap index with 60 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1879 B Sitemaps referenced 8 User-agents LinkedInBot, Google-InspectionTool, PanguBot, Diffbot, DuckAssistBot, archive.org_bot, FacebookExternalHit, AmazonAdBot, GoogleOther, meta-externalfetcher, ClaudeBot, PetalBot, Webzio, heritrix, cohere-ai, Google-Extended, Amazonbot, Claude-User, MistralAI-User, Webzio-Extended, Pinterestbot, CCBot, Bytespider, Storebot-Google, Google-CloudVertexBot, Applebot-Extended, *, cohere-training-data-crawler, Timpibot, ia_archiver, Perplexity-User, TikTokSpider, meta-webindexer, meta-externalagent, Claude-SearchBot, PerplexityBot, ia_archiver-web.archive.org, Twitterbot Blocking No — crawling allowed
Sitemap: https://www.allure.com/sitemap.xml
Sitemap: https://www.allure.com/tagpages-sitemap.xml
Sitemap: https://www.allure.com/contributors-sitemap.xml
Sitemap: https://www.allure.com/bundles-sitemap.xml
Sitemap: https://www.allure.com/branded-sitemap.xml
Sitemap: https://www.allure.com/feed/google-latest-news/sitemap-google-news
Sitemap: https://www.allure.com/feed/rss
Sitemap: https://www.allure.com/feed/met-gala-feed/rss

User-agent: *
Disallow: /*?
Allow: /*?*page
Allow: /*.xml?
Allow: /*.js
Allow: /*.css
Allow: /*.ico
Allow: /verso/static
Allow: /*.svg
Allow: /*.png
Allow: /*.jpg
Allow: /*.jpeg
Allow: /*rss?
Allow: /*?id=
Disallow: /auth/
Disallow: /account/
Disallow: /user/
Disallow: /user-context
Disallow: /preview/
Disallow: /search
Disallow: /product/
Disallow: /cdn-cgi/
Disallow: /services.min.js
Disallow: /com.condenast/yv8

###
Allow: /product/listing/
###

User-agent: FacebookExternalHit
User-agent: Twitterbot
User-agent: Pinterestbot
User-agent: LinkedInBot
User-agent: TikTokSpider
User-agent: Storebot-Google
User-agent: Google-InspectionTool
User-agent: AmazonAdBot
Allow: /

User-agent: Google-Extended
User-agent: Google-CloudVertexBot
User-agent: GoogleOther
User-agent: Applebot-Extended
User-agent: Amazonbot
User-agent: meta-webindexer
User-agent: meta-externalagent
User-agent: meta-externalfetcher
User-agent: ClaudeBot
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: PerplexityBot
User-agent: Perplexity-User
User-agent: cohere-training-data-crawler
User-agent: cohere-ai
User-agent: CCBot
User-agent: PanguBot
User-agent: PetalBot
User-agent: Bytespider
User-agent: Diffbot
User-agent: DuckAssistBot
User-agent: MistralAI-User
User-agent: Timpibot
User-agent: Webzio
User-agent: Webzio-Extended
User-agent: archive.org_bot
User-agent: ia_archiver
User-agent: ia_archiver-web.archive.org
User-agent: heritrix
Disallow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 60 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
allure.com — via CSC Corporate Domains, Inc., 32 years, 4 months old
PASS
allure.com — via CSC Corporate Domains, Inc., 32 years, 4 months old
Info::
Domain registered until May 18, 2027 (1 years, 1 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: CSC Corporate Domains, Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Domain expiry

336 days

May 18, 2027

SSL certificate

213 days

Issued by Amazon

Domain age

32 years, 4 months

Registered May 17, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:9000:a41b:ef95:eff:32b3:411c:f36c

Registrar

CSC Corporate Domains, Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created May 17, 1994 (32 years, 4 months ago)
Expires May 18, 2027 (1 years, 1 months)
Last Updated May 14, 2025
Name Servers ns-1116.awsdns-11.org, ns-1935.awsdns-49.co.uk, ns-28.awsdns-03.com, ns-836.awsdns-40.net
DNSSEC Not enabled
Hosting
IP Address 2600:9000:a41b:ef95:eff:32b3:411c:f36c
Data source: rdap (0.1s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 143 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
35 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
71 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
143 ms
Total Time Total request time from DNS lookup through full response.
144 ms

Connection waterfall

DNS Lookup 35 ms TCP Connect 1 ms TLS Handshake 71 ms Server Processing 37 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback