Skip to content
https://eepurl.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
4 PASS 5 REVIEW
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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

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

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

301http://eepurl.com/ http://mailchimp.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

193
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
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A
DNS Records
1 A records, 12 ms lookup
PASS
1 A records, 12 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.201.160.160
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: a6-66.akam.net, a1-205.akam.net, a14-66.akam.net, a4-65.akam.net, a5-65.akam.net, a7-66.akam.net
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
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: 12 ms
Got: 12 ms
A23.201.160.160
AAAA
CNAME
NSa6-66.akam.net, a1-205.akam.net, a14-66.akam.net, a4-65.akam.net, a5-65.akam.net, a7-66.akam.net
MX
TXT
_z0wc6vmvjbvcm5fp3gts295gq1nqf8d
95hl48p0xjbqydr7xyzz8ptmksl1334w
_8hkh7i00e0luex039dp6fsfjhs4bk8u
_lgool0gg7wzos9kz40nbb40e86izja0
spycloud-domain-verification=2127e2b7-da8a-44df-95f5-c77882a949b1
_72ru7fr8c0ncfmjg71hyedfisw40m4h
524t8ygzcd8l07x0v7bhq882qj55dgsw
CAALookup not available with standard resolver
Resolved in 12 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.

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
Redirect Chain
1 redirect(s), 76 ms total
PASS
1 redirect(s), 76 ms total
Info::
Single redirect
Got: https://eepurl.com → https://mailchimp.com/ (301)
Info::
Cross-domain redirect detected

https://eepurl.com

18 ms · HTTP/1.1

301

https://mailchimp.com/

57 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://eepurl.com30118 msHTTP/1.1AkamaiGHost
2https://mailchimp.com/20057 msHTTP/1.1istio-envoy

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
eepurl.com — via MarkMonitor Inc., 17 years, 6 months old, hosted on Akamai
PASS
eepurl.com — via MarkMonitor Inc., 17 years, 6 months old, hosted on Akamai
Info::
Domain registered until Dec 22, 2031 (5 years, 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: MarkMonitor 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: Akamai
Got: AS16625
Domain expiry

2016 days

December 22, 2031

SSL certificate

193 days

Issued by DigiCert Inc

Domain age

17 years, 6 months

Registered December 22, 2008

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS16625

23.66.205.125

Registrar

MarkMonitor Inc.

Unlocked 6 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 MarkMonitor Inc.
Created December 22, 2008 (17 years, 6 months ago)
Expires December 22, 2031 (5 years, 9 months)
Last Updated October 15, 2024
Name Servers a1-205.akam.net, a14-66.akam.net, a4-65.akam.net, a5-65.akam.net, a6-66.akam.net, a7-66.akam.net
DNSSEC Not enabled
Hosting
IP Address 23.66.205.125
ASN AS16625 (AKAMAI-AS - Akamai Technologies, Inc., US)
Provider Akamai
Data source: rdap (0.1s)

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

Connection waterfall

DNS Lookup 7 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 6 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