Skip to content
https://wellficent.com

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 Madrid, Spain
302 Found
Checks
17
8 PASS 8 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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 69.46.46.50: lookup 69.46.46.50: 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 63ms across 3 resolvers (spread 159ms)
REVIEW
Mean 63ms across 3 resolvers (spread 159ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Google: 30ms
Got: 30ms via 8.8.8.8:53
Info::
Cloudflare: 160ms
Got: 160ms via 1.1.1.1: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
TLS Certificate Expiry & Recommendations
60 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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.
A
DNS Records
1 A records, 514 ms lookup
PASS
1 A records, 514 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 69.46.46.50
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: ns2.dns-parking.com, ns1.dns-parking.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (514 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 514 ms
A69.46.46.50
AAAA—
CNAME—
NSns2.dns-parking.com, ns1.dns-parking.com
MX
10 inbound1.sendinblue.com
20 inbound2.sendinblue.com
TXT
google-site-verification=b65sIJRrN4k8eVRsVXPwUpxBENxnEYWmkcmkAiVqGYI
brevo-code:fe4f1011c2a0d99a02ea8743d21ba965
SPF v=spf1 include:spf.brevo.com ~all
CAALookup not available with standard resolver
Resolved in 514 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
1 redirect(s), 177 ms total
PASS
1 redirect(s), 177 ms total
Info::
Single redirect
Got: https://wellficent.com → https://wellficent.com/en/ (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://wellficent.com

https://wellficent.com

145 ms · HTTP/1.1

302

https://wellficent.com/en/

33 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://wellficent.com302145 msHTTP/1.1railway-hikari
2https://wellficent.com/en/20033 msHTTP/1.1railway-hikari

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
Crawlability
robots.txt present, sitemap with 21 URLs
PASS
robots.txt present, sitemap with 21 URLs
Info::
robots.txt is present
Got: 191 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 21 entries
Info::
Sitemap index with 21 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 191 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /_private/
Disallow: /config/
Disallow: /tools/
Disallow: /src/

Sitemap: https://wellficent.com/sitemap.xml
Sitemap: https://wellficent.com/news-sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 21 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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
wellficent.com — via HOSTINGER operations, UAB, 1 years, 2 months old, hosted on RAILWAY - Railway, US
PASS
wellficent.com — via HOSTINGER operations, UAB, 1 years, 2 months old, hosted on RAILWAY - Railway, US
Info::
Domain registered until Aug 17, 2027 (9 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: HOSTINGER operations, UAB
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: RAILWAY - Railway, US
Got: AS400940
Domain expiry

282 days

August 17, 2027

SSL certificate

60 days

Issued by Let's Encrypt

Domain age

1 years, 2 months

Registered August 17, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

RAILWAY - Railway, US

ASN AS400940

69.46.46.50

Registrar

HOSTINGER operations, UAB

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 HOSTINGER operations, UAB
Created August 17, 2025 (1 years, 2 months ago)
Expires August 17, 2027 (9 months)
Last Updated July 21, 2026
Name Servers ns1.dns-parking.com, ns2.dns-parking.com
DNSSEC Not enabled
Hosting
IP Address 69.46.46.50
ASN AS400940 (RAILWAY - Railway, US)
Provider RAILWAY - Railway, US
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 34 ms TCP Connect 26 ms TLS Handshake 29 ms Server Processing 33 ms Content Transfer 0 ms
A+
Health Check Endpoint
Health endpoint at https://wellficent.com/healthz (HTTP 200)
PASS
Health endpoint at https://wellficent.com/healthz (HTTP 200)
Info::
Public health endpoint at https://wellficent.com/healthz
Got: https://wellficent.com/healthz
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback