Skip to content
https://abc.xyz

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Singapore, Singapore
200 OK
Checks
9
6 PASS 3 REVIEW
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 207 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

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.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 207 B Sitemaps referenced 0 User-agents *, Eluta.ca, MS Search 6.0 Robot, gsa-crawler Blocking No — crawling allowed
User-agent: *

Crawl-delay: 10
Allow: /


User-agent: Eluta.ca

Crawl-delay: 60
Allow: /


User-agent: MS Search 6.0 Robot

Crawl-delay: 60
Allow: /


User-agent: gsa-crawler

Crawl-delay: 60
Allow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.abc.xyz/
200https://abc.xyz/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://abc.xyz/ https://abc.xyz/

Consistent

B
TLS Certificate Expiry & Recommendations
75 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

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 Records
2 A records, 7 ms lookup
PASS
2 A records, 7 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 162.159.130.11, 162.159.129.11
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:7::a29f:810b, 2606:4700:7::a29f:820b
Info::
4 nameserver(s) configured
Got: ns2.google.com, ns3.google.com, ns4.google.com, ns1.google.com
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 7 ms
Got: 7 ms
A162.159.130.11, 162.159.129.11
AAAA2606:4700:7::a29f:810b, 2606:4700:7::a29f:820b
CNAME
NSns2.google.com, ns3.google.com, ns4.google.com, ns1.google.com
MX
0 smtp.google.com
TXT
facebook-domain-verification=cwepyxwq7zq6o0yr4he2uanjdjy99v
google-site-verification=p3s4_zTt2xb14TEn4ULQ4bxNjA2ElFyFhutWaWHoDOk
SPF v=spf1 include:_spf.google.com include:_spf.q4press.com ~all
CAALookup not available with standard resolver
Resolved in 7 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://abc.xyz

https://abc.xyz

40 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://abc.xyz20040 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700:7::a29f:810b, 2606:4700:7::a29f:820b
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700:7::a29f:810b, 2606:4700:7::a29f:820b Connection Reachable (1 ms)
A+
Domain Intelligence
abc.xyz — via MarkMonitor, Inc (TLDs), 12 years, 3 months old
PASS
abc.xyz — via MarkMonitor, Inc (TLDs), 12 years, 3 months old
Info::
Domain registered until Mar 20, 2027 (11 months remaining)
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: MarkMonitor, Inc (TLDs)
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.
Domain expiry

280 days

March 20, 2027

SSL certificate

75 days

Issued by Google Trust Services

Domain age

12 years, 3 months

Registered March 20, 2014

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:7::a29f:810b

Registrar

MarkMonitor, Inc (TLDs)

Unlocked 4 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor, Inc (TLDs)
Created March 20, 2014 (12 years, 3 months ago)
Expires March 20, 2027 (11 months)
Last Updated March 6, 2026
Name Servers ns2.google.com, ns4.google.com, ns3.google.com, ns1.google.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:7::a29f:810b
Data source: rdap (0.9s)

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 272 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
4 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
271 ms
Total Time Total request time from DNS lookup through full response.
272 ms

Connection waterfall

DNS Lookup 4 ms TCP Connect 1 ms TLS Handshake 8 ms Server Processing 258 ms Content Transfer 1 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: SIN)
Got: cf-ray: 9f088ac75c98c5bc-SIN
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: 9f088ac75c98c5bc-SIN
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback