Skip to content
https://huangguoai.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
5
PASS
11
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
11 PASS 5 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2600:9000:25f0:aa00:3:fdd6:fcc0:93a1, 2600:9000:25f0:9c00:3:fdd6:fcc0:93a1, 2600:9000:25f0:7e00:3:fdd6:fcc0:93a1, 2600:9000:25f0:be00:3:fdd6:fcc0:93a1, 2600:9000:25f0:8200:3:fdd6:fcc0:93a1, 2600:9000:25f0:cc00:3:fdd6:fcc0:93a1, 2600:9000:25f0:8a00:3:fdd6:fcc0:93a1, 2600:9000:25f0:4600:3:fdd6:fcc0:93a1
Info::
IPv6 connection error
Got: dial tcp6 [2600:9000:25f0:aa00:3:fdd6:fcc0:93a1]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2600:9000:25f0:aa00:3:fdd6:fcc0:93a1, 2600:9000:25f0:9c00:3:fdd6:fcc0:93a1, 2600:9000:25f0:7e00:3:fdd6:fcc0:93a1, 2600:9000:25f0:be00:3:fdd6:fcc0:93a1, 2600:9000:25f0:8200:3:fdd6:fcc0:93a1, 2600:9000:25f0:cc00:3:fdd6:fcc0:93a1, 2600:9000:25f0:8a00:3:fdd6:fcc0:93a1, 2600:9000:25f0:4600:3:fdd6:fcc0:93a1 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/12 IPs match cert SAN
REVIEW
0/12 IPs match cert SAN
Info::
PTR for 18.244.214.28 does not match any cert SAN: server-18-244-214-28.sfo53.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 18.244.214.65 does not match any cert SAN: server-18-244-214-65.sfo53.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 18.244.214.78 does not match any cert SAN: server-18-244-214-78.sfo53.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 18.244.214.89 does not match any cert SAN: server-18-244-214-89.sfo53.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR lookup failed for 2600:9000:25f0:aa00:3:fdd6:fcc0:93a1: lookup 2600:9000:25f0:aa00:3:fdd6:fcc0:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:9000:25f0:9c00:3:fdd6:fcc0:93a1: lookup 2600:9000:25f0:9c00:3:fdd6:fcc0:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:9000:25f0:7e00:3:fdd6:fcc0:93a1: lookup 2600:9000:25f0:7e00:3:fdd6:fcc0:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:9000:25f0:be00:3:fdd6:fcc0:93a1: lookup 2600:9000:25f0:be00:3:fdd6:fcc0:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:9000:25f0:8200:3:fdd6:fcc0:93a1: lookup 2600:9000:25f0:8200:3:fdd6:fcc0:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:9000:25f0:cc00:3:fdd6:fcc0:93a1: lookup 2600:9000:25f0:cc00:3:fdd6:fcc0:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:9000:25f0:8a00:3:fdd6:fcc0:93a1: lookup 2600:9000:25f0:8a00:3:fdd6:fcc0:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:9000:25f0:4600:3:fdd6:fcc0:93a1: lookup 2600:9000:25f0:4600:3:fdd6:fcc0:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
TLS Certificate Expiry & Recommendations
195 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

195
days left
0d 30d 60d 90d+

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable DNSSEC on your domain for DNS spoofing protection
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
DNS Records
4 A records, 18 ms lookup
PASS
4 A records, 18 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 18.244.214.28, 18.244.214.65, 18.244.214.78, 18.244.214.89
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:25f0:aa00:3:fdd6:fcc0:93a1, 2600:9000:25f0:9c00:3:fdd6:fcc0:93a1, 2600:9000:25f0:7e00:3:fdd6:fcc0:93a1, 2600:9000:25f0:be00:3:fdd6:fcc0:93a1, 2600:9000:25f0:8200:3:fdd6:fcc0:93a1, 2600:9000:25f0:cc00:3:fdd6:fcc0:93a1, 2600:9000:25f0:8a00:3:fdd6:fcc0:93a1, 2600:9000:25f0:4600:3:fdd6:fcc0:93a1
Info::
2 nameserver(s) configured
Got: olivia.ns.cloudflare.com, peyton.ns.cloudflare.com
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 18 ms
Got: 18 ms
A18.244.214.28, 18.244.214.65, 18.244.214.78, 18.244.214.89
AAAA2600:9000:25f0:aa00:3:fdd6:fcc0:93a1, 2600:9000:25f0:9c00:3:fdd6:fcc0:93a1, 2600:9000:25f0:7e00:3:fdd6:fcc0:93a1, 2600:9000:25f0:be00:3:fdd6:fcc0:93a1, 2600:9000:25f0:8200:3:fdd6:fcc0:93a1, 2600:9000:25f0:cc00:3:fdd6:fcc0:93a1, 2600:9000:25f0:8a00:3:fdd6:fcc0:93a1, 2600:9000:25f0:4600:3:fdd6:fcc0:93a1
CNAME—
NSolivia.ns.cloudflare.com, peyton.ns.cloudflare.com
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 18 ms

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 15ms across 3 resolvers (spread 12ms)
PASS
Mean 15ms across 3 resolvers (spread 12ms)
Info::
Quad9: 10ms
Got: 10ms via 9.9.9.9:53
Info::
Google: 15ms
Got: 15ms via 8.8.8.8:53
Info::
Cloudflare: 22ms
Got: 22ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://huangguoai.com

https://huangguoai.com

30 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://huangguoai.com20030 msHTTP/1.1nginx/1.22.1
A+
Crawlability
robots.txt present, sitemap with 10 URLs
PASS
robots.txt present, sitemap with 10 URLs
Info::
robots.txt is present
Got: 611 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 10 entries
Info::
Sitemap index with 10 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 611 B Sitemaps referenced 3 User-agents ChatGPT-User, GPTBot, ClaudeBot, PerplexityBot, CCBot, Bytespider, *, OAI-SearchBot Blocking No — crawling allowed
Sitemap: https://huangguoai.com/sitemap.xml
Sitemap: https://huangguoai.com/video-sitemap.xml
Sitemap: https://huangguoai.com/sitemap-topic.xml

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: CCBot
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: *
Disallow: /admin/
Disallow: /admin
Disallow: /api/
Disallow: /profile/
Disallow: /upload/
Disallow: /cdn-cgi/l/email-protection
Disallow: /search/
Disallow: /login/
Disallow: /register/
Allow: /*?page=
Disallow: /*?*
sitemap.xml 200 OK
Type Sitemap Index URLs 10 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.huangguoai.com/
200https://huangguoai.com/

Preferred variant: non-www

HTTP → HTTPS

301http://huangguoai.com/ → https://huangguoai.com/

Consistent

A+
Domain Intelligence
huangguoai.com — via GoDaddy.com, LLC, 3 months old, hosted on AWS
PASS
huangguoai.com — via GoDaddy.com, LLC, 3 months old, hosted on AWS
Info::
Domain registered until Jul 15, 2028 (1 years, 9 months remaining)
Info::
Domain is only 3 months old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Jul 15, 2026
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: GoDaddy.com, LLC
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

631 days

July 15, 2028

SSL certificate

195 days

Issued by Amazon

Domain age

3 months

Registered July 15, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

18.244.214.28

Registrar

GoDaddy.com, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created July 15, 2026 (3 months ago)
Expires July 15, 2028 (1 years, 9 months)
Last Updated October 8, 2026
Name Servers olivia.ns.cloudflare.com, peyton.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 18.244.214.28
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.1s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

Why this matters

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

A+
HTTP Probe Timing
Total 25 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
10 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
3 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
23 ms
Total Time Total request time from DNS lookup through full response.
26 ms

Connection waterfall

DNS Lookup 10 ms TCP Connect 3 ms TLS Handshake 5 ms Server Processing 5 ms Content Transfer 3 ms
A+
CDN & Delivery
AWS CloudFront (Hit from cloudfront)
PASS
AWS CloudFront (Hit from cloudfront)
Info::
Document is served via AWS CloudFront CDN (edge: SFO53-P4)
Got: x-amz-cf-id: NThTKr-Wv50GskAboctB8AKiwv2TADBzlDpiva6nqcdep1oAr1CS_A==
Info::
CDN cache status: Hit from cloudfront
Document served via CDN: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: NThTKr-Wv50GskAboctB8AKiwv2TADBzlDpiva6nqcdep1oAr1CS_A==
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 2 header(s)
Got: age=3606, x-cache=Hit from cloudfront
A+
Health Check Endpoint
Health endpoint at https://huangguoai.com/health (HTTP 200)
PASS
Health endpoint at https://huangguoai.com/health (HTTP 200)
Info::
Public health endpoint at https://huangguoai.com/health
Got: https://huangguoai.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback