Skip to content
https://ammarexe.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
0
REVIEW
8
PASS
9
INFO
0
Probed from Singapore, Singapore
307 Temporary Redirect
Checks
17
9 PASS 8 REVIEW
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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 216.198.79.1: lookup 216.198.79.1: 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
Multi-Resolver DNS Speed
Mean 146ms across 3 resolvers (spread 159ms)
REVIEW
Mean 146ms across 3 resolvers (spread 159ms)
Info::
Quad9: 43ms
Got: 43ms via 9.9.9.9:53
Info::
Cloudflare: 195ms
Got: 195ms via 1.1.1.1:53
Info::
Google: 202ms
Got: 202ms via 8.8.8.8:53
B
Redirect Chain
1 redirect(s), 1027 ms total
REVIEW
1 redirect(s), 1027 ms total
Info::
Single redirect
Got: https://ammarexe.com → https://ammarexe.com/dashboard (307)
Warning::
Redirect overhead: 1027 ms total
Got: 1027 ms

https://ammarexe.com

768 ms · HTTP/1.1

307

https://ammarexe.com/dashboard

258 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ammarexe.com307768 msHTTP/1.1Vercel
2https://ammarexe.com/dashboard200258 msHTTP/1.1Vercel

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

C
TLS Certificate Expiry & Recommendations
Action
28 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

28
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 28 days remaining
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
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.
A
DNS Records
1 A records, 576 ms lookup
PASS
1 A records, 576 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 216.198.79.1
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: ns1.dyna-ns.net, ns2.dyna-ns.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (576 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 576 ms
A216.198.79.1
AAAA—
CNAME—
NSns1.dyna-ns.net, ns2.dyna-ns.net
MX
0 webhost.dynadot.com
TXT
SPF v=spf1 mx include:webhost-mail-out.dynadot.com include:spf.webhost.dynadot.com ~...
CAALookup not available with standard resolver
Resolved in 576 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
Crawlability
no robots.txt, sitemap with 271 URLs
PASS
no robots.txt, sitemap with 271 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 271 entries

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 308

www / non-www

307https://www.ammarexe.com/
200https://ammarexe.com/

HTTP → HTTPS

308http://ammarexe.com/ → https://ammarexe.com/

Consistent

A+
Domain Intelligence
ammarexe.com — via Dynadot Inc, 2 months old, hosted on AWS
PASS
ammarexe.com — via Dynadot Inc, 2 months old, hosted on AWS
Info::
Domain registered until Aug 25, 2027 (10 months remaining)
Info::
Domain is only 2 months old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Aug 25, 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: Dynadot 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: AWS
Got: AS16509
Domain expiry

303 days

August 25, 2027

SSL certificate

28 days

Issued by Let's Encrypt

Domain age

2 months

Registered August 25, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

216.198.79.1

Registrar

Dynadot Inc

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Dynadot Inc
Created August 25, 2026 (2 months ago)
Expires August 25, 2027 (10 months)
Last Updated August 25, 2026
Name Servers ns1.dyna-ns.net, ns2.dyna-ns.net
DNSSEC Not enabled
Hosting
IP Address 216.198.79.1
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (1.2s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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 798 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
503 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.
14 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
798 ms
Total Time Total request time from DNS lookup through full response.
798 ms

Connection waterfall

DNS Lookup 503 ms TCP Connect 1 ms TLS Handshake 14 ms Server Processing 280 ms Content Transfer 0 ms
A
CDN & Delivery
Vercel (MISS)
PASS
Vercel (MISS)
Info::
Document is served via Vercel CDN
Got: x-vercel-id: sin1::iad1::wlsw6-1792948905146-b6f3c5120a90
Info::
CDN cache status: MISS
Document served via CDN: Vercel
Provider Vercel Cache Status MISS Evidence x-vercel-id: sin1::iad1::wlsw6-1792948905146-b6f3c5120a90
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 2 header(s)
Got: age=0, x-vercel-cache=MISS
A+
Health Check Endpoint
Auth-protected health endpoint at https://ammarexe.com/health (HTTP 403)
PASS
Auth-protected health endpoint at https://ammarexe.com/health (HTTP 403)
Info::
Auth-protected health endpoint exposed at https://ammarexe.com/health
Got: https://ammarexe.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback