Skip to content
https://amaporn.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
9
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
7 PASS 9 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
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.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 51.89.2.208 does not match any cert SAN: ip208.ip-51-89-2.eu
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
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.amaporn.com/
200https://amaporn.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://amaporn.com/ https://www.amaporn.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
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
1 A records, 40 ms lookup
PASS
1 A records, 40 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 51.89.2.208
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: jerry.ns.cloudflare.com, tina.ns.cloudflare.com
Info::
5 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: 40 ms
Got: 40 ms
A51.89.2.208
AAAA
CNAME
NSjerry.ns.cloudflare.com, tina.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
google-site-verification=_8tXxZg_1E90p2YRODnc7OjCJmgdp-Po9jPxPwgXGf4
google-site-verification=tfIk81Ur5cjp2d4L12HR2_ViyKd7sWmA2-af3vpyPVU
google-site-verification=Zy0btSInEC9IA01NbTnnToT9Cb-4NJGi8if297ifGhc
CAALookup not available with standard resolver
Resolved in 40 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

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 37ms across 3 resolvers (spread 36ms)
PASS
Mean 37ms across 3 resolvers (spread 36ms)
Info::
Cloudflare: 21ms
Got: 21ms via 1.1.1.1:53
Info::
Google: 33ms
Got: 33ms via 8.8.8.8:53
Info::
Quad9: 57ms
Got: 57ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 301 ms total
PASS
1 redirect(s), 301 ms total
Info::
Single redirect
Got: https://amaporn.com → https://www.amaporn.com/ (301)
Info::
WWW normalization redirect

https://amaporn.com

119 ms · HTTP/1.1

301

https://www.amaporn.com/

182 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://amaporn.com301119 msHTTP/1.1nginx
2https://www.amaporn.com/200182 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 209 URLs
PASS
robots.txt present, sitemap with 209 URLs
Info::
robots.txt is present
Got: 841 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 209 entries
Info::
Sitemap index with 209 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 841 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /player/float.php
Disallow: /player/html.php
Disallow: /redirect_cs.php
Disallow: /*?action=*$
Disallow: /*mode=async*$
Disallow: /*function=get_block*$
Disallow: /404.php
Disallow: /logout/
Disallow: /email/
Disallow: /payments/
Disallow: /login/
Disallow: /login-required/
Disallow: /signup/
Disallow: /upgrade/
Disallow: /reset-password/
Disallow: /resend-confirmation/
Disallow: /invite/
Disallow: /feedback/
Disallow: /categories-selector/
Disallow: /models-selector/
Disallow: /captcha/*
Disallow: /link/*
Disallow: /related_videos_html/*
Disallow: /embed/* 
Disallow: /json_categories.php
Disallow: /check_login.php
Disallow: /json_comment_feed.php
Disallow: /json_following_feed.php
Disallow: /get_video_url.php
Disallow: /json_reel_feed.php
Disallow: /members/*/
Sitemap: https://www.amaporn.com/sitemap.xml

sitemap.xml 200 OK
Type Sitemap Index URLs 209 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
amaporn.com — via GoDaddy.com, LLC, 20 years, 2 months old, hosted on OVH
PASS
amaporn.com — via GoDaddy.com, LLC, 20 years, 2 months old, hosted on OVH
Info::
Domain registered until Aug 28, 2027 (1 years 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: GoDaddy.com, LLC
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: OVH
Got: AS16276
Domain expiry

376 days

August 28, 2027

SSL certificate

73 days

Issued by Let's Encrypt

Domain age

20 years, 2 months

Registered August 28, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

51.89.2.208

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC
Created August 28, 2006 (20 years, 2 months ago)
Expires August 28, 2027 (1 years)
Last Updated August 5, 2026
Name Servers jerry.ns.cloudflare.com, tina.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 51.89.2.208
ASN AS16276 (OVH - OVH SAS, FR)
Provider OVH
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 36 ms TCP Connect 26 ms TLS Handshake 57 ms Server Processing 36 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