Skip to content
https://mailenable.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
77
GRADE
C
FIX
2
REVIEW
4
PASS
3
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
9
3 PASS 4 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.mailenable.com/
200https://mailenable.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

200http://mailenable.com/

HTTP version does not redirect to HTTPS

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
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
Domain Intelligence
mailenable.com — via eNom, LLC, 25 years, 4 months old, hosted on COGECO-PEER1 - Aptum Technologies, CA
REVIEW
mailenable.com — via eNom, LLC, 25 years, 4 months old, hosted on COGECO-PEER1 - Aptum Technologies, CA
Critical::
Domain expires in 7 days
This domain expires on April 30, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Got: Expires Apr 30, 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: eNom, 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: COGECO-PEER1 - Aptum Technologies, CA
Got: AS13768
Domain expiry

EXPIRED

April 30, 2026

SSL certificate

338 days

Issued by Sectigo Limited

Domain age

25 years, 4 months

Registered April 30, 2001

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

COGECO-PEER1 - Aptum Technologies, CA

ASN AS13768

216.157.69.92

Registrar

eNom, LLC

Unlocked 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar eNom, LLC
Created April 30, 2001 (25 years, 4 months ago)
Expires April 30, 2026 (7 days)
Last Updated April 25, 2025
Name Servers dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com
DNSSEC Not enabled
Hosting
IP Address 216.157.69.92
ASN AS13768 (COGECO-PEER1 - Aptum Technologies, CA)
Provider COGECO-PEER1 - Aptum Technologies, CA
Data source: rdap (0.6s)

This domain expires on April 30, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

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

B
HTTP Probe Timing
Total 1246 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
137 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
110 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
131 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.14 s
Total Time Total request time from DNS lookup through full response.
1.25 s

Connection waterfall

DNS Lookup 137 ms TCP Connect 110 ms TLS Handshake 131 ms Server Processing 758 ms Content Transfer 110 ms
B
TLS Certificate Expiry & Recommendations
338 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

338
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
A
DNS Records
1 A records, 267 ms lookup
PASS
1 A records, 267 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 216.157.69.92
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: dns2.name-services.com, dns4.name-services.com, dns5.name-services.com, dns3.name-services.com, dns1.name-services.com
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (267 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 267 ms
A216.157.69.92
AAAA
CNAME
NSdns2.name-services.com, dns4.name-services.com, dns5.name-services.com, dns3.name-services.com, dns1.name-services.com
MX
10 mail.mailenable.com
TXT
SPF v=spf1 ip4:216.157.69.92 a mx -all
google-site-verification=pEUP_BPep3lAi-tIB1C6h1R2T1Xk83vM-lblIreBvB4
CAALookup not available with standard resolver
Resolved in 267 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://mailenable.com

https://mailenable.com

345 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mailenable.com200345 msHTTP/1.1Microsoft-IIS/10.0
A+
Crawlability
robots.txt present, sitemap with 878 URLs
PASS
robots.txt present, sitemap with 878 URLs
Info::
robots.txt is present
Got: 687 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 878 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 687 B Sitemaps referenced 1 User-agents Barkrowler, ClaudeBot, meta-externalagent, *, SemrushBot, BLEXBot, MJ12bot, AhrefsBot Blocking No — crawling allowed
User-agent: *

Allow: /

Disallow: /mobile/*

Disallow: /documentation/1.0/*

Disallow: /documentation/2.0/*

Disallow: /documentation/3.0/*

Disallow: /documentation/4.0/*

Disallow: /documentation/5.0/*

Disallow: /documentation/6.0/*

Disallow: /documentation/7.0/*

Disallow: /documentation/8.0/*

Disallow: /documentation/9.0/*

Disallow: /mewebmail/*


Sitemap: http://www.mailenable.com/sitemap.xml


User-agent: SemrushBot

Disallow: /


User-agent: BLEXBot

Disallow: /


User-agent: MJ12bot

Disallow: /


User-agent: AhrefsBot

Disallow: /


User-agent: Barkrowler

Disallow: /


User-agent: ClaudeBot

Disallow: /


User-agent: meta-externalagent

Disallow: /forum/


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

Send Feedback