Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DHTTP Probe TimingActionTotal 2869 ms — DNS, TCP, TLS, TTFB, content transfer breakdownFIX
Connection waterfall
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNS Records3 A records, 612 ms lookupREVIEW
| A | 180.76.198.77, 180.76.198.225, 180.76.199.13 |
| AAAA | — |
| CNAME | gitee.com-31ba39d0fd3.baiduads.com |
| NS | sv3.bdydns.cn, sv4.bdydns.cn, sv2.bdydns.cn, sv1.bdydns.cn |
| MX | 5 mxn.mxhichina.com 10 mxw.mxhichina.com |
| TXT | google-site-verification=k6g67wLcX8hKzHFbfHt-Ut6_65yEgKa7FEnABMG1vE4 SPF v=spf1 include:spf.qiye.aliyun.com -all |
| CAA | Lookup not available with standard resolver |
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
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.
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
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, 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
### BEGIN FILE ###
#
# allow-all
#
#
User-agent: *
Crawl-delay: 1
Disallow: /admin/
Disallow: /api/v*
Disallow: /*/*/archive/refs/tags/*
Disallow: /*/*/blame/*
Disallow: /*/*/commit/*
Disallow: /*/*/commits/*
Disallow: /*/*/compare/*
Disallow: /*/*/contributors
Disallow: /*/*/git-upload-pack
Disallow: /*/*/graph/*
Disallow: /*/*/info/refs
Disallow: /*/*/pulls/*/commits
Disallow: /*/*/pulls/*/files
Disallow: /*/*/raw/*
Disallow: /*/*/releases/download/*
Disallow: /*/*/repository/archive/*
Disallow: /*/*/repository/stats/*
Disallow: /*/*/tree/*
Sitemap: https://gitee.com/sitemaps/sitemap.xml.gz
### END FILE ###
BTLS Certificate Expiry & Recommendations304 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+Redirect ChainNo redirects — direct accessPASS
https://gitee.com
2030 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://gitee.com | 200 | 2030 ms | HTTP/1.1 | ADAS/1.0.214 |
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencegitee.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 17 years, 4 months old, hosted on CHINATELECOM-SHANDONG-JINAN-IDC Jinan,250000, CNPASS
597 days
March 4, 2028
304 days
Issued by TrustAsia Technologies, Inc.
17 years, 4 months
Registered March 4, 2009
Not enabled
Protects against DNS spoofing
CHINATELECOM-SHANDONG-JINAN-IDC Jinan,250000, CN
ASN AS58540
180.76.198.225
Alibaba Cloud Computing (Beijing) Co., Ltd.
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