Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BTLS Certificate Expiry & Recommendations32 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
A+DNS Records3 A records, 37 ms lookupPASS
| A | 104.26.11.24, 104.26.10.24, 172.67.69.155 |
| AAAA | 2606:4700:20::ac43:459b, 2606:4700:20::681a:b18, 2606:4700:20::681a:a18 |
| CNAME | — |
| NS | vern.ns.cloudflare.com, rachel.ns.cloudflare.com |
| MX | 10 mail.muffingroup.com |
| TXT | SPF v=spf1 a mx ip4:167.235.206.58 ip4:49.12.114.118 ip4:135.181.191.69 ~all 2a58ea2a8fec52e2ef8fda4a35e26c55086b51bf105405b16646975ca6d3ccb google-site-verification=6snpuWM3ll32NdIavyECOdLHPdU9Sre0tfKP5cbDPpQ |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Redirect ChainNo redirects — direct accessPASS
https://muffingroup.com
69 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://muffingroup.com | 200 | 69 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 380 URLsPASS
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
User-agent: *
Disallow: /api/
Disallow: /cms/
Disallow: /dev8624/
Disallow: /sandbox/
Disallow: /robocze/
Disallow: /themeforest_images/
Disallow: /html/
Disallow: /forum/ripson/
Disallow: /themes/ripson/
Disallow: /doc/
Disallow: /splash/
Disallow: /iframe/
Disallow: /themeforest_images/
Disallow: /nc6z/
Disallow: *1000*
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencemuffingroup.com — via PDR Ltd. d/b/a PublicDomainRegistry.com, 14 years, 5 months oldPASS
178 days
January 11, 2027
32 days
Issued by Google Trust Services
14 years, 5 months
Registered January 11, 2012
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:20::681a:b18
PDR Ltd. d/b/a PublicDomainRegistry.com
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