Skip to content
https://dazeddigital.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
4 PASS 4 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
Redirect Chain
1 redirect(s), 2547 ms total
REVIEW
1 redirect(s), 2547 ms total
Info::
Single redirect
Got: https://dazeddigital.com → https://www.dazeddigital.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2547 ms total
Got: 2547 ms

https://dazeddigital.com

599 ms · HTTP/1.1

301

https://www.dazeddigital.com/

1949 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://dazeddigital.com301599 msHTTP/1.1Microsoft-IIS/10.0
2https://www.dazeddigital.com/2001949 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

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.dazeddigital.com/
200https://dazeddigital.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://dazeddigital.com/ → https://dazeddigital.com/

Consistent

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

Certificate validity

194
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
1 A records, 100 ms lookup
PASS
1 A records, 100 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 13.69.228.44
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns3.livedns.co.uk, ns2.livedns.co.uk, ns1.livedns.co.uk
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::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 100 ms
Got: 100 ms
A13.69.228.44
AAAA—
CNAME—
NSns3.livedns.co.uk, ns2.livedns.co.uk, ns1.livedns.co.uk
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
facebook-domain-verification=pv5u77edh6b11dc1r3mfu017ha3qzh
80ar418gl7v4mdlrs70of16s30
google-site-verification=qXhIVMktzJKC_U0hvtLhwAcMCWIeJz0ROGjwsBB08Ks
klaviyo-site-verification=YsDqRL
google-site-verification=JV-Ilry0v4uHGyjmky2nlW7CHcJKwnu_wTs-tZJeN6s
743CC5B6633FBEFFA235A3F604961A925C7DA8ED9C850632729B000F52DF3908
lj37cestvceim4n7t6lv49omkm
google-site-verification=f_pE4hdZtQ51zGwzaed-aul4lfxVrUgrZwixim_1L5Q
google-site-verification=NsRJ2qS9ZxUF4Q27oL5nV3Kcf4xHSsTp0Rb7X8gR4Hc
tollbit-domain-verification=82935a8d49e7ca7eac2f69f68051939bc9b25cb37370a40c3166...
ur4d29phiqgh0uvsa8tk4vr78n
CAALookup not available with standard resolver
Resolved in 100 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Crawlability
robots.txt present, sitemap with 5914 URLs
PASS
robots.txt present, sitemap with 5914 URLs
Info::
robots.txt is present
Got: 1016 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 5914 entries
Info::
Sitemap index with 5914 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 1016 B Sitemaps referenced 0 User-agents *, GPTBot, CCBot, ChatGPT-User Blocking No — crawling allowed
User-agent: *

# allowRobotsTxtUrl: https://www.dazeddigital.com/robots.txt

# url: https://www.dazeddigital.com/robots.txt

Disallow: /search/*

Disallow: /admin/

Disallow: /account/

Disallow: /Subscriber/CreateWidget

Disallow: /beauty/politics/*

Disallow: /beauty/life-culture/*

Disallow: /beauty/science-tech/*

Disallow: /beauty/film-tv/*

Disallow: /beauty/art-photography/*

Disallow: /beauty/music/*

Disallow: /beauty/fashion/*

Disallow: /body/*

Disallow: /soul/*

Disallow: /head/*

Disallow: /community/*

Disallow: /masculinity/*

Disallow: /article/ListJson*

Disallow: /article/ArticleListJson*

Disallow: /article/listjson*

Disallow: /article/articlelistjson*

Disallow: /Article/ListJson*

Disallow: /Article/ArticleListJson*

Disallow: /beauty/article/ListJson*

Disallow: /beauty/article/ArticleListJson*

Disallow: /beauty/Article/ListJson*

Disallow: /beauty/Article/ArticleListJson*

User-agent: GPTBot

Disallow: /

User-agent: CCBot

Disallow: /

User-agent: ChatGPT-User

Disallow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 5914 entries Valid XML Yes
Child Sitemaps:
A
Domain Intelligence
dazeddigital.com — via IONOS SE, 20 years, 1 months old, hosted on Microsoft Azure
PASS
dazeddigital.com — via IONOS SE, 20 years, 1 months old, hosted on Microsoft Azure
Warning::
Domain expires in 68 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 30, 2026
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: IONOS SE
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.
Info::
Hosting: Microsoft Azure
Got: AS8075
Domain expiry

14 days

June 30, 2026

SSL certificate

194 days

Issued by GoDaddy.com, Inc.

Domain age

20 years, 1 months

Registered June 30, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

13.69.228.44

Registrar

IONOS SE

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar IONOS SE
Created June 30, 2006 (20 years, 1 months ago)
Expires June 30, 2026 (2 months)
Last Updated February 3, 2026
Name Servers ns1.livedns.co.uk, ns2.livedns.co.uk, ns3.livedns.co.uk
DNSSEC Not enabled
Hosting
IP Address 13.69.228.44
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: rdap (0.2s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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 573 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
22 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
136 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
278 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
573 ms
Total Time Total request time from DNS lookup through full response.
573 ms

Connection waterfall

DNS Lookup 22 ms TCP Connect 136 ms TLS Handshake 278 ms Server Processing 138 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