Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/4 IPs match cert SANREVIEW
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
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
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: SpeedDownload
Disallow: /
User-agent: MJ12bot
Disallow: /
User-agent: discobot
Disallow: /
User-agent: dotbot
Disallow: /
User-agent: psbot
Disallow: /
User-agent: Exabot
Disallow: /
User-agent: sitebot
Disallow: /
User-agent: findxbot
Disallow: /
User-agent: AhrefsBot
Disallow: /
User-agent: *
Disallow: /wiki/Special
Disallow: /wiki/User
Disallow: /wiki/User_talk
Disallow: /wiki/MediaWiki
Disallow: /wiki/MediaWiki_talk
Disallow: /wiki/Talk
Disallow: /wiki/index.php
Disallow: /wiki/api.php
Disallow: /wiki/File:
Allow: /
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations46 days until leaf cert expires — 2 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
BOperational Status PageNo status page link detectedREVIEW
BHealth Check EndpointNo conventional health endpoint foundREVIEW
A+DNS Records2 A records, 37 ms lookupPASS
| A | 188.114.96.2, 188.114.97.2 |
| AAAA | 2a06:98c1:3120::2, 2a06:98c1:3121::2 |
| CNAME | — |
| NS | maya.ns.cloudflare.com, bruce.ns.cloudflare.com |
| MX | 10 mx.zoho.com 20 mx2.zoho.com 30 mx3.zoho.com |
| TXT | google-site-verification=ABsepH-gTI8bvNhsbgggqKJ2VRJIZavVAzvQVNlnx-8 SPF v=spf1 include:zoho.com ~all |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 15ms across 3 resolvers (spread 16ms)PASS
ARedirect Chain1 redirect(s), 779 ms totalPASS
https://wikiporno.org
313 ms · HTTP/1.1
https://www.wikiporno.org/
466 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://wikiporno.org | 301 | 313 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.wikiporno.org/ | 200 | 466 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Domain Intelligencewikiporno.org — via NameSilo, LLC, 19 years, 9 months oldPASS
173 days
January 11, 2027
46 days
Issued by Google Trust Services
19 years, 9 months
Registered January 11, 2007
Not enabled
Protects against DNS spoofing
Unknown
2a06:98c1:3121::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