Infrastructure
· 9 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.
BRedirect Chain2 redirect(s), 185 ms totalREVIEW
https://dafont.com
63 ms · HTTP/1.1
https://www.dafont.com/
84 ms · HTTP/1.1
https://www.dafont.com/fr/
39 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://dafont.com | 301 | 63 ms | HTTP/1.1 | Apache/2.4.66 |
| 2 | https://www.dafont.com/ | 302 | 84 ms | HTTP/1.1 | Apache/2.4.66 |
| 3 | https://www.dafont.com/fr/ | 200 | 39 ms | HTTP/1.1 | Apache/2.4.66 |
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
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
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
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: Mediapartners-Google
Disallow:
User-agent: *
Disallow: /dl.php
Disallow: /download/
Disallow: /pselectlist.php
Disallow: /pselectuser.php
Disallow: /submit.php
Disallow: /contact.php
Disallow: /search.php
Disallow: /alpha.php
Disallow: /xmas.php
Disallow: /adisplay.php
Disallow: /login.php
Disallow: /register.php
Disallow: /forum/goto.php
Disallow: /fr/pselectlist.php
Disallow: /fr/pselectuser.php
Disallow: /fr/submit.php
Disallow: /fr/contact.php
Disallow: /fr/search.php
Disallow: /fr/alpha.php
Disallow: /fr/adisplay.php
Disallow: /fr/login.php
Disallow: /fr/register.php
Disallow: /fr/forum/goto.php
Disallow: /es/pselectlist.php
Disallow: /es/pselectuser.php
Disallow: /es/submit.php
Disallow: /es/contact.php
Disallow: /es/search.php
Disallow: /es/alpha.php
Disallow: /es/adisplay.php
Disallow: /es/login.php
Disallow: /es/register.php
Disallow: /es/forum/goto.php
Disallow: /de/pselectlist.php
Disallow: /de/pselectuser.php
Disallow: /de/submit.php
Disallow: /de/contact.php
Disallow: /de/search.php
Disallow: /de/alpha.php
Disallow: /de/adisplay.php
Disallow: /de/login.php
Disallow: /de/register.php
Disallow: /de/forum/goto.php
Disallow: /it/pselectlist.php
Disallow: /it/pselectuser.php
Disallow: /it/submit.php
Disallow: /it/contact.php
Disallow: /it/search.php
Disallow: /it/alpha.php
Disallow: /it/adisplay.php
Disallow: /it/login.php
Disallow: /it/register.php
Disallow: /it/forum/goto.php
Disallow: /pt/pselectlist.php
Disallow: /pt/pselectuser.php
Disallow: /pt/submit.php
Disallow: /pt/contact.php
Disallow: /pt/search.php
Disallow: /pt/alpha.php
Disallow: /pt/adisplay.php
Disallow: /pt/login.php
Disallow: /pt/register.php
Disallow: /pt/forum/goto.php
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations162 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- 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 Records1 A records, 36 ms lookupPASS
| A | 87.98.168.164 |
| AAAA | — |
| CNAME | — |
| NS | b.dns.gandi.net, a.dns.gandi.net, c.dns.gandi.net |
| MX | 1 ASPMX.L.GOOGLE.com 3 ALT2.ASPMX.L.GOOGLE.com 3 ALT1.ASPMX.L.GOOGLE.com 5 ASPMX3.GOOGLEMAIL.com 5 ASPMX2.GOOGLEMAIL.com 5 ASPMX4.GOOGLEMAIL.com 5 ASPMX5.GOOGLEMAIL.com |
| TXT | SPF v=spf1 ip4:87.98.168.164 include:_spf.google.com -all google-site-verification=eZ8fw6oYR6lP-mdEBpaem37NgHXAs32puRywvaI3mjo |
| 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
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+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencedafont.com — via Gandi SAS, 25 years, 10 months old, hosted on OVHPASS
486 days
October 15, 2027
162 days
Issued by Gandi SAS
25 years, 10 months
Registered October 15, 2000
Not enabled
Protects against DNS spoofing
OVH
ASN AS16276
87.98.168.164
Gandi SAS
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