Skip to content
https://atexflow.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 7 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

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.
C
Reverse DNS
Action
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 185.73.228.142: lookup 185.73.228.142: 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 185.30.124.158: lookup 185.30.124.158: 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.
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
TLS Certificate Expiry & Recommendations
84 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

84
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
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
2 A records, 47 ms lookup
PASS
2 A records, 47 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 185.73.228.142, 185.30.124.158
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns2.gcdn.services, ns1.gcorelabs.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 47 ms
Got: 47 ms
A185.73.228.142, 185.30.124.158
AAAA—
CNAME—
NSns2.gcdn.services, ns1.gcorelabs.net
MX
100 mail.webwavecms.com
TXT
google-site-verification=tGerVfMSMzB8Rxh4utPY2wDbA6NNSyIccNzRk4eLnx0
SPF v=spf1 include:spf._cname.webwavecms.com -all
CAALookup not available with standard resolver
Resolved in 47 ms
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 45ms across 3 resolvers (spread 54ms)
PASS
Mean 45ms across 3 resolvers (spread 54ms)
Info::
Quad9: 26ms
Got: 26ms via 9.9.9.9:53
Info::
Google: 30ms
Got: 30ms via 8.8.8.8:53
Info::
Cloudflare: 80ms
Got: 80ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://atexflow.com

https://atexflow.com

142 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://atexflow.com200142 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 15 URLs
PASS
robots.txt present, sitemap with 15 URLs
Info::
robots.txt is present
Got: 55 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 15 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 55 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Sitemap: https://atexflow.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 15 entries Valid XML Yes
Sample URLs:
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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.atexflow.com/
200https://atexflow.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
atexflow.com — via OVH sas, 19 days old, hosted on ETOP-AS - eTOP sp. z o.o., PL
PASS
atexflow.com — via OVH sas, 19 days old, hosted on ETOP-AS - eTOP sp. z o.o., PL
Info::
Domain registered until Oct 14, 2027 (11 months remaining)
Info::
Domain is only 19 days 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 Oct 14, 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: OVH sas
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: ETOP-AS - eTOP sp. z o.o., PL
Got: AS20853
Domain expiry

339 days

October 14, 2027

SSL certificate

84 days

Issued by Let's Encrypt

Domain age

19 days

Registered October 14, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

ETOP-AS - eTOP sp. z o.o., PL

ASN AS20853

185.73.228.142

Registrar

OVH sas

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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar OVH sas
Created October 14, 2026 (19 days ago)
Expires October 14, 2027 (11 months)
Last Updated October 14, 2026
Name Servers ns1.webwavecms.com, ns2.webwavecms.com
DNSSEC Not enabled
Hosting
IP Address 185.73.228.142
ASN AS20853 (ETOP-AS - eTOP sp. z o.o., PL)
Provider ETOP-AS - eTOP sp. z o.o., PL
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 50 ms TCP Connect 45 ms TLS Handshake 50 ms Server Processing 51 ms Content Transfer 86 ms
A+
CDN Cache Observability
Cache state: Age=59805s
PASS
Cache state: Age=59805s
Info::
CDN cache state observable via 1 header(s)
Got: age=59805
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback