Skip to content
https://magiceraser.live

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Santa Clara, United States
308 Permanent Redirect
Checks
17
8 PASS 8 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700:20::681a:4c4, 2606:4700:20::ac43:46d0, 2606:4700:20::681a:5c4
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:20::681a:4c4]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700:20::681a:4c4, 2606:4700:20::ac43:46d0, 2606:4700:20::681a:5c4 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/6 IPs match cert SAN
REVIEW
0/6 IPs match cert SAN
Info::
PTR lookup failed for 104.26.4.196: lookup 104.26.4.196: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 172.67.70.208: lookup 172.67.70.208: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 104.26.5.196: lookup 104.26.5.196: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:20::681a:4c4: lookup 2606:4700:20::681a:4c4: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:20::ac43:46d0: lookup 2606:4700:20::ac43:46d0: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:20::681a:5c4: lookup 2606:4700:20::681a:5c4: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
TLS Certificate Expiry & Recommendations
88 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: a1b9b836b98ea709-SJC
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: a1b9b836b98ea709-SJC
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
3 A records, 28 ms lookup
PASS
3 A records, 28 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.4.196, 172.67.70.208, 104.26.5.196
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::681a:4c4, 2606:4700:20::ac43:46d0, 2606:4700:20::681a:5c4
Info::
2 nameserver(s) configured
Got: memphis.ns.cloudflare.com, sue.ns.cloudflare.com
Info::
1 mail exchanger(s) configured
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: 28 ms
Got: 28 ms
A104.26.4.196, 172.67.70.208, 104.26.5.196
AAAA2606:4700:20::681a:4c4, 2606:4700:20::ac43:46d0, 2606:4700:20::681a:5c4
CNAME—
NSmemphis.ns.cloudflare.com, sue.ns.cloudflare.com
MX
1 smtp.google.com
TXT
google-site-verification=EEF55N7pHJnEnroBEZ_ZGh_3N_Ag235hNpBifviN9Bo
google-site-verification=SLbACd1QQoTtdbubngdXa2mlCPABNE2oxMWo5k7IRbc
google-site-verification=hcC4i1iTXUWbCERgz6m2G7cvZp6A8R7PAaLZIj4kgCM
google-site-verification=v9NFw9ZjQomfx4x_9I2F44dwYHhzYOdTIslZ0vbnQYU
CAALookup not available with standard resolver
Resolved in 28 ms

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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 8ms across 3 resolvers (spread 11ms)
PASS
Mean 8ms across 3 resolvers (spread 11ms)
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Quad9: 6ms
Got: 6ms via 9.9.9.9:53
Info::
Google: 15ms
Got: 15ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 400 ms total
PASS
1 redirect(s), 400 ms total
Info::
Single redirect
Got: https://magiceraser.live → https://magiceraser.live/en (308)

https://magiceraser.live

81 ms · HTTP/1.1

308

https://magiceraser.live/en

319 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://magiceraser.live30881 msHTTP/1.1cloudflare
2https://magiceraser.live/en200319 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 13 URLs
PASS
robots.txt present, sitemap with 13 URLs
Info::
robots.txt is present
Got: 686 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 13 entries
Info::
Sitemap index with 13 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 686 B Sitemaps referenced 1 User-agents anthropic-ai, Applebot-Extended, ChatGPT-User, CCBot, Bytespider, Google-Extended, ClaudeBot, PerplexityBot, OAI-SearchBot, Amazonbot, cohere-ai, *, GPTBot Blocking No — crawling allowed
User-Agent: *
Allow: /
Disallow: /download
Disallow: /*/download
Disallow: /home
Disallow: /*/home
Disallow: /*?q=
Disallow: /*&q=
Disallow: /*?*sort=
Disallow: /*?*filter=
Disallow: /*?*order=
Disallow: /*?*page=
Disallow: /*?*ref=

User-Agent: GPTBot
Allow: /

User-Agent: Google-Extended
Allow: /

User-Agent: ClaudeBot
Allow: /

User-Agent: anthropic-ai
Allow: /

User-Agent: PerplexityBot
Allow: /

User-Agent: Applebot-Extended
Allow: /

User-Agent: ChatGPT-User
Allow: /

User-Agent: OAI-SearchBot
Allow: /

User-Agent: CCBot
Allow: /

User-Agent: Amazonbot
Allow: /

User-Agent: Bytespider
Allow: /

User-Agent: cohere-ai
Allow: /

Sitemap: https://magiceraser.live/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 13 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.magiceraser.live/
200https://magiceraser.live/

Preferred variant: non-www

HTTP → HTTPS

301http://magiceraser.live/ → https://magiceraser.live/

Consistent

A+
Domain Intelligence
magiceraser.live — via Name.com, Inc., 4 years, 3 months old, hosted on Cloudflare
PASS
magiceraser.live — via Name.com, Inc., 4 years, 3 months old, hosted on Cloudflare
Info::
Domain registered until Apr 8, 2027 (8 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: Name.com, 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.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

266 days

April 8, 2027

SSL certificate

88 days

Issued by Google Trust Services

Domain age

4 years, 3 months

Registered April 8, 2022

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.26.4.196

Registrar

Name.com, Inc.

Unlocked 2 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 Name.com, Inc.
Created April 8, 2022 (4 years, 3 months ago)
Expires April 8, 2027 (8 months)
Last Updated March 22, 2026
Name Servers sue.ns.cloudflare.com, memphis.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 104.26.4.196
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 26 ms TCP Connect 3 ms TLS Handshake 9 ms Server Processing 540 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