Skip to content
https://abc13.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
7 PASS 2 REVIEW
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

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

Certificate validity

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

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+
DNS Records
4 A records, 55 ms lookup
PASS
4 A records, 55 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 18.245.175.81, 18.245.175.30, 18.245.175.108, 18.245.175.69
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1394.awsdns-46.org, ns-691.awsdns-22.net, ns-162.awsdns-20.com, ns-1692.awsdns-19.co.uk
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: 55 ms
Got: 55 ms
A18.245.175.81, 18.245.175.30, 18.245.175.108, 18.245.175.69
AAAA
CNAME
NSns-1394.awsdns-46.org, ns-691.awsdns-22.net, ns-162.awsdns-20.com, ns-1692.awsdns-19.co.uk
MX
0 abc13-com.mail.protection.outlook.com
TXT
SPF v=spf1 include:spf.protection.outlook.com -all
CAALookup not available with standard resolver
Resolved in 55 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://abc13.com

https://abc13.com

420 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://abc13.com200420 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 1000 URLs
PASS
robots.txt present, sitemap with 1000 URLs
Info::
robots.txt is present
Got: 677 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1000 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 677 B Sitemaps referenced 3 User-agents claritybot, Google-Extended, CCBot, ChatGPT-User, Omgilibot, Omgili, *, GPTBot, anthropic-ai, FacebookBot, Bytespider Blocking No — crawling allowed
Sitemap: https://abc13.com/sitemap/ktrk/stories.xml
Sitemap: https://abc13.com/sitemap/ktrk/categories.xml
Sitemap: https://abc13.com/sitemap/ktrk/videos.xml

User-agent: *
Disallow: /common/
Disallow: /external/
Disallow: /extras/reporttypo/
Disallow: /thirdparty/
Disallow: /users/
Disallow: /staging/
Disallow: /test/

User-agent: claritybot
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: Omgilibot
Disallow: /

User-agent: Omgili
Disallow: /

User-agent: FacebookBot
Disallow: /

User-agent: Bytespider
Disallow: /

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 301-redirects to HTTPS

www / non-www

302https://www.abc13.com/
200https://abc13.com/

Preferred variant: non-www

HTTP → HTTPS

301http://abc13.com/ https://abc13.com/

Consistent

A+
Domain Intelligence
abc13.com — via CSC Corporate Domains, Inc., 26 years, 7 months old, hosted on AWS
PASS
abc13.com — via CSC Corporate Domains, Inc., 26 years, 7 months old, hosted on AWS
Info::
Domain registered until Feb 4, 2027 (9 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: CSC Corporate Domains, Inc.
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

234 days

February 4, 2027

SSL certificate

166 days

Issued by Amazon

Domain age

26 years, 7 months

Registered February 4, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

18.245.175.81

Registrar

CSC Corporate Domains, Inc.

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 CSC Corporate Domains, Inc.
Created February 4, 2000 (26 years, 7 months ago)
Expires February 4, 2027 (9 months)
Last Updated January 5, 2026
Name Servers ns-1394.awsdns-46.org, ns-162.awsdns-20.com, ns-1692.awsdns-19.co.uk, ns-691.awsdns-22.net
DNSSEC Not enabled
Hosting
IP Address 18.245.175.81
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 52 ms TCP Connect 16 ms TLS Handshake 19 ms Server Processing 373 ms Content Transfer 168 ms
A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: CDG55-P1)
Got: x-amz-cf-id: kzklG4liknWlxIRmAdok2cE20ME8AHwJ4v5AAI3ZN6rv1ZzBgI_WUA==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: kzklG4liknWlxIRmAdok2cE20ME8AHwJ4v5AAI3ZN6rv1ZzBgI_WUA==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback