Skip to content
https://amandaai.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
10
PASS
6
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
6 PASS 10 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.

C
DNSSEC
Action
Zone signed but parent has no DS record
REVIEW
Zone signed but parent has no DS record
Warning::
DNSSEC keys published but parent zone has no DS record
The zone publishes DNSKEY records but the registry has not been updated with the corresponding DS record. From a validating resolver's perspective the domain is unsigned. Submit the DS record to your registrar to complete the delegation.
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.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 46.16.234.100 does not match any cert SAN: haus-srv01.oderland.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
C
Multi-Resolver DNS Speed
Action
Mean 208ms across 3 resolvers (spread 144ms)
REVIEW
Mean 208ms across 3 resolvers (spread 144ms)
Info::
Cloudflare: 152ms
Got: 152ms via 1.1.1.1:53
Info::
Google: 177ms
Got: 177ms via 8.8.8.8:53
Info::
Quad9: 296ms
Got: 296ms via 9.9.9.9:53
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
HTTP Probe Timing
Total 1065 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
292 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
154 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
156 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
757 ms
Total Time Total request time from DNS lookup through full response.
1.07 s

Connection waterfall

DNS Lookup 292 ms TCP Connect 154 ms TLS Handshake 156 ms Server Processing 154 ms Content Transfer 309 ms
B
TLS Certificate Expiry & Recommendations
72 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

72
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
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: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A
DNS Records
1 A records, 316 ms lookup
PASS
1 A records, 316 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 46.16.234.100
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns02.one.com, ns01.one.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (316 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 316 ms
A46.16.234.100
AAAA—
CNAME—
NSns02.one.com, ns01.one.com
MX
0 amandaai-com.mail.protection.outlook.com
TXT
google-site-verification=CXSsuheowLXpjgtD3Bw7tqH5xaVYeF9tt_MJvfTntAY
SPF v=spf1 include:spf.protection.outlook.com include:_custspf.one.com include:14599...
linkedin-site-verification=d3560522-82f1-4528-b1a7-9884cbeefb63
upsales-customer-domain-verification=01c3ab67aa60cfc41d3fd4c4322b21b9
CAALookup not available with standard resolver
Resolved in 316 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

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://amandaai.com

https://amandaai.com

801 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://amandaai.com200801 msHTTP/1.1LiteSpeed
A+
Crawlability
robots.txt present, sitemap with 12 URLs
PASS
robots.txt present, sitemap with 12 URLs
Info::
robots.txt is present
Got: 116 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 12 entries
Info::
Sitemap index with 12 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 116 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://amandaai.com/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 12 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::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.amandaai.com/
200https://amandaai.com/

HTTP → HTTPS

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

Consistent

A
Domain Intelligence
amandaai.com — via One.com A/S, 7 years, 10 months old, hosted on ASODERLAND, SE
PASS
amandaai.com — via One.com A/S, 7 years, 10 months old, hosted on ASODERLAND, SE
Warning::
Domain expires in 88 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Aug 7, 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: One.com A/S
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: ASODERLAND, SE
Got: AS44136
Domain expiry

84 days

August 7, 2026

SSL certificate

72 days

Issued by Let's Encrypt

Domain age

7 years, 10 months

Registered August 7, 2018

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

ASODERLAND, SE

ASN AS44136

46.16.234.100

Registrar

One.com A/S

Unlocked 2 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 One.com A/S
Created August 7, 2018 (7 years, 10 months ago)
Expires August 7, 2026 (2 months)
Last Updated July 8, 2025
Name Servers ns01.one.com, ns02.one.com
DNSSEC Not enabled
Hosting
IP Address 46.16.234.100
ASN AS44136 (ASODERLAND, SE)
Provider ASODERLAND, SE
Data source: rdap (0.4s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback