Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction3 redirect(s), 628 ms totalFIX
https://bigrocco.com
263 ms · HTTP/1.1
https://www.g2fame.com/RoccoSiffredi/go....
53 ms · HTTP/1.1
https://www.roccosiffredi.com/track/go.p...
140 ms · HTTP/1.1
https://lp.roccosiffredi.com/track/go.ph...
172 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://bigrocco.com | 301 | 263 ms | HTTP/1.1 | Apache/2 |
| 2 | https://www.g2fame.com/RoccoSiffredi/go.... | 301 | 53 ms | HTTP/1.1 | cloudflare |
| 3 | https://www.roccosiffredi.com/track/go.p... | 301 | 140 ms | HTTP/1.1 | cloudflare |
| 4 | https://lp.roccosiffredi.com/track/go.ph... | 200 | 172 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
BReverse DNS0/1 IPs match cert SANREVIEW
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"/><meta name="mobile-web-app-capable" content="yes"><meta name="apple-mobile-web-app-capable" content="yes"><meta name="theme-color" content="#000000"/><link rel="manifest" href="/manifest.json"/><link rel="preconnect" href="wp8q3hdhdz-dsn.algolia.net"><script defer="defer" src="/static/js/main.516bd22c.js" type="5feb20bf81fcc9ac1cc816b1-text/javascript"></script><link href="/static/css/main.6530ace7.css" rel="stylesheet"></head><body><noscript>You need to enable JavaScript to run this app.</noscript><div id="root"></div><!-- Cloudflare Pages Analytics --><script defer src='https://static.cloudflareinsights.com/beacon.min.js' data-cf-beacon='{"token": "83dd24f14f534e24b4d78b7bf7f4c088"}' type="5feb20bf81fcc9ac1cc816b1-text/javascript"></script><!-- Cloudflare Pages Analytics --><script src="/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js" data-cf-settings="5feb20bf81fcc9ac1cc816b1-|49" defer></script></body></html>
BTLS Certificate Expiry & Recommendations78 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
CCDN & DeliveryActionAssets on AWS CloudFront (host ctf-images.gammacdn.com, 21 assets); document served directly from originREVIEW
Asset hosts on a CDN
- ctf-images.gammacdn.com — AWS CloudFront · assets: 21 · Cache Status: Hit from cloudfront
- jumpto.fun — AWS CloudFront · assets: 4 · Cache Status: Error from cloudfront
Other asset hosts
- static01-cms-evilangel.gammacdn.com — assets: 2 · below probe threshold
- d3a3ewgd1iewwz.cloudfront.net — assets: 1 · below probe threshold
- static.cloudflareinsights.com — assets: 1 · below probe threshold
- static03-cms-fame.gammacdn.com — assets: 1 · below probe threshold
- www.roccosiffredi.com — assets: 1 · below probe threshold
The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
ADNS Records1 A records, 779 ms lookupPASS
| A | 208.122.217.2 |
| AAAA | — |
| CNAME | — |
| NS | ns2.vm3644.eosdns.net, ns1.vm3644.eosdns.net |
| MX | 10 mail.bigrocco.com |
| TXT | SPF v=spf1 a mx ip4:208.122.217.2 ~all |
| 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
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
AMulti-Resolver DNS SpeedMean 50ms across 3 resolvers (spread 45ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencebigrocco.com — via NameSilo, LLC, 9 years, 9 months old, hosted on MOJOHOST - MOJOHOST, USPASS
125 days
January 31, 2027
78 days
Issued by Let's Encrypt
9 years, 9 months
Registered January 31, 2017
Not enabled
Protects against DNS spoofing
MOJOHOST - MOJOHOST, US
ASN AS27589
208.122.217.2
NameSilo, 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