Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/1 IPs match cert SANREVIEW
CMulti-Resolver DNS SpeedActionMean 101ms across 3 resolvers (spread 274ms)REVIEW
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>ManuelFerrara.com - Age Verification</title>
<link rel="stylesheet" href="styles.css">
<style>
body {
margin: 0;
font-family: Arial, sans-serif;
background-color: #f4f4f4;
color: #333;
min-height: 100vh;
display: flex;
flex-direction: column;
justify-content: space-between;
align-items: center;
padding: 0;
box-sizing: border-box;
}
.header {
width: 100%;
max-width: 100%;
height: auto;
}
.container {
background-color: rgba(255, 255, 255, 0.9);
padding: 20px;
border-radius: 8px;
box-shadow: 0 4px 8px rgba(0, 0, 0, 0.2);
width: 75%;
max-width: 1200px;
text-align: left;
position: absolute;
bottom: 25%;
left: 50%;
transform: translateX(-50%);
}
.footer-container {
background-color: rgba(255, 255, 255, 0.9);
padding: 15px;
border-radius: 8px;
box-shadow: 0 4px 8px rgba(0, 0, 0, 0.2);
width: 75%;
max-width: 1200px;
text-align: center;
margin-bottom: 5px;
}
.footer-container a {
color: #000;
text-decoration: underline;
margin: 0 5px;
}
.footer-container a:hover {
text-decoration: underline;
}
h1 {
font-size: 24px;
color: #000;
text-align: center;
}
p {
font-size: 16px;
margin: 10px 0;
}
.cta-button {
display: inline-block;
margin-top: 20px;
padding: 10px 20px;
font-size: 16px;
color: #fff;
border: none;
border-radius: 5px;
text-decoration: none;
cursor: pointer;
transition: background-color 0.3s;
}
.cta-button:hover {
opacity: 0.9;
}
.cta-button.verify-age {
background-color: #28a745;
}
.cta-button.current-members {
background-color: #fd7e14;
}
.button-group {
display: flex;
justify-content: center;
gap: 10px;
margin-top: 20px;
}
@media (max-width: 768px) {
.container {
position: relative;
margin-top: 10px;
width: 95%;
}
body {
overflow-x: hidden;
}
}
@media (min-width: 769px) {
.container {
position: absolute;
bottom: 25%;
left: 50%;
transform: translateX(-50%);
}
}
</style>
<script>
document.addEventListener("DOMContentLoaded", function () {
const yearSpan = document.getElementById("current-year");
yearSpan.textContent = new Date().getFullYear();
});
</script>
</head>
<body>
<img src="pg_mf_header.jpg" alt="Header" class="header">
<div class="container">
<h1>Age Verification Required</h1>
<p>Welcome to <strong>ManuelFerrara.com</strong>!</p>
<p>You’ve been redirected here because your location requires age verification to access adult content on our site.</p>
<p>To comply with local regulations and ensure a safe browsing experience, we must confirm that you are at least 18 years old (or the age of majority in your jurisdiction).</p>
<p><strong>What Happens Next?</strong></p>
<ul>
<li>You will be prompted to complete a quick and secure age verification process.</li>
<li>Once verified, you’ll have unrestricted access to all content on <strong>ManuelFerrara.com</strong>.</li>
</ul>
<p>We appreciate your understanding and cooperation in helping us comply with local laws.</p>
<div class="button-group">
<a href="https://enter.manuelferrara.com/signup/signup.php?nats=MC4wLjcuMTYuMC4wLjAuMC4w&step=2" class="cta-button verify-age">Verify Age</a>
<a href="https://www.manuelferrara.com/verifymyage/" class="cta-button current-members">Current Members</a>
</div>
</div>
<div class="footer-container">
For billing inquiries, customer support or to cancel your membership, please visit:
<a href="#">Support</a> | <a href="#">Contact Us</a> | <a href="#">Terms</a> | <a href="#">Privacy Policy</a> | <a href="#">Report Content</a> | <a href="#">Webmasters</a>
<br>
<a href="https://www.manuelferrara.com/2257.html">18 U.S.C. 2257 Record-Keeping Requirements Compliance Statement</a>
<br>
Copyright © 2006 - <span id="current-year">2025</span> ManuelFerrara.com, All Rights Reserved
</div>
</body>
</html>
BTLS Certificate Expiry & Recommendations176 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
ADNS Records1 A records, 43 ms lookupPASS
| A | 216.18.168.47 |
| AAAA | — |
| CNAME | — |
| NS | ns1.reflected.net, ns0.reflected.net |
| MX | 10 mail.manuelferrara.com |
| TXT | — |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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'.
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 TakeoverNo subdomain takeover risk detectedPASS
ARedirect Chain1 redirect(s), 376 ms totalPASS
https://manuelferrara.com
79 ms · HTTP/1.1
https://www.manuelferrara.com/trial_pg/
298 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://manuelferrara.com | 302 | 79 ms | HTTP/1.1 | |
| 2 | https://www.manuelferrara.com/trial_pg/ | 200 | 298 ms | HTTP/1.1 | Apache/2.4.66 (Debian) |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
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+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencemanuelferrara.com — via Register.com - Network Solutions, LLC, 23 years, 6 months old, hosted on REFLECTED - Reflected Networks, Inc., USPASS
284 days
April 25, 2027
176 days
Issued by Sectigo Limited
23 years, 6 months
Registered April 25, 2003
Not enabled
Protects against DNS spoofing
REFLECTED - Reflected Networks, Inc., US
ASN AS29789
216.18.168.47
Register.com - Network Solutions, LLC
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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