Skip to content
https://comscore.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
0
REVIEW
6
PASS
3
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
3 PASS 6 REVIEW
B
Redirect Chain
1 redirect(s), 1109 ms total
REVIEW
1 redirect(s), 1109 ms total
Info::
Single redirect
Got: https://comscore.com → https://www.comscore.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1109 ms total
Got: 1109 ms

https://comscore.com

104 ms · HTTP/1.1

301

https://www.comscore.com/

1004 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://comscore.com301104 msHTTP/1.1CloudFront
2https://www.comscore.com/2001004 msHTTP/1.1CloudFront

See the visual redirect chain in the HTTP Probe tab →

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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 989 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 989 B Sitemaps referenced 0 User-agents *, AhrefsBot Blocking No — crawling allowed
User-agent: *
Crawl-delay: 10
# /comscore/search added to stop google / bing / etc indexing search restuls pages, which should not be in index and can lead to unwanted trafic from bots
Disallow: /comscore/search
# Block query strings
Disallow: /*?
Disallow: /request/
Disallow: /*/request/
Disallow: /drafts/
Disallow: /*/drafts/
Disallow: /rss_items/
Disallow: /*/rss_items/
Disallow: /redirects/
Disallow: /*/redirects/
Disallow: /cmr/
Disallow: /*/cmr/
Disallow: /layout/set/popup/
Disallow: /*/layout/set/popup/
Disallow: /*.pdf$
Disallow: /rus$
Disallow: /dut$
Disallow: /rus/*
Disallow: /dut/*

Disallow: /Request/
Disallow: /*/Request/
Disallow: /Drafts/
Disallow: /*/Drafts/
Disallow: /Rss_items/
Disallow: /*/Rss_items/
Disallow: /Redirects/
Disallow: /*/Redirects/
Disallow: /Cmr/
Disallow: /*/Cmr/
Disallow: /Layout/set/popup/
Disallow: /*/Layout/set/popup/
Disallow: /*.Pdf$
Disallow: /Rus$
Disallow: /Dut$
Disallow: /Rus/*
Disallow: /Dut/*

User-agent: AhrefsBot
Disallow: /


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.comscore.com/
200https://comscore.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://comscore.com/ https://comscore.com/

Consistent

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

Certificate validity

204
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
B
CDN & Delivery
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
REVIEW
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: GRU1-P4)
Got: x-amz-cf-id: WD4g8DsEAR0V8hFZICY4rvQObzwT7rs46p1qbk665rgRsFRYHEc0vA==
Info::
CDN cache status: FunctionGeneratedResponse from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status FunctionGeneratedResponse from cloudfront Evidence x-amz-cf-id: WD4g8DsEAR0V8hFZICY4rvQObzwT7rs46p1qbk665rgRsFRYHEc0vA==
A+
DNS Records
4 A records, 93 ms lookup
PASS
4 A records, 93 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 3.164.6.99, 3.164.6.104, 3.164.6.87, 3.164.6.73
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1432.awsdns-51.org, ns-1643.awsdns-13.co.uk, ns-230.awsdns-28.com, ns-536.awsdns-03.net
Info::
2 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: 93 ms
Got: 93 ms
A3.164.6.99, 3.164.6.104, 3.164.6.87, 3.164.6.73
AAAA
CNAME
NSns-1432.awsdns-51.org, ns-1643.awsdns-13.co.uk, ns-230.awsdns-28.com, ns-536.awsdns-03.net
MX
10 mxa-00648602.gslb.pphosted.com
20 mxb-00648602.gslb.pphosted.com
TXT
anthropic-domain-verification-xg4es4=vzyCkCapu9jN3AgprKJUxWIzm
atlassian-domain-verification=YkFCb0foqM46WDjtByjKMN0-m6gvQywdoz+7yvTvPc7JT8G3u3...
google-site-verification=5JT-rfiLFkasOA17ypIRGcBCN1aiLWux3nqqDzxGbKE
jamf-site-verification=ikJwtmN1OP2veuua-cfNZQ
openai-domain-verification=dv-LuZabvqxhbRDgig28mNah78i
SPF v=spf1 ip4:216.109.78.236/32 ip4:216.109.78.239/32 ip4:52.12.147.15/32 ip4:66.11...
CAALookup not available with standard resolver
Resolved in 93 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+
Domain Intelligence
comscore.com — via MarkMonitor Inc., 27 years, 1 months old, hosted on AWS
PASS
comscore.com — via MarkMonitor Inc., 27 years, 1 months old, hosted on AWS
Info::
Domain registered until Jul 26, 2026 (3 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.
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

40 days

July 26, 2026

SSL certificate

204 days

Issued by Amazon

Domain age

27 years, 1 months

Registered July 26, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

3.164.6.73

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created July 26, 1999 (27 years, 1 months ago)
Expires July 26, 2026 (3 months)
Last Updated June 24, 2025
Name Servers ns-1432.awsdns-51.org, ns-1643.awsdns-13.co.uk, ns-230.awsdns-28.com, ns-536.awsdns-03.net
DNSSEC Not enabled
Hosting
IP Address 3.164.6.73
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.7s)

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 30 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
21 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 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.
31 ms
Total Time Total request time from DNS lookup through full response.
31 ms

Connection waterfall

DNS Lookup 21 ms TCP Connect 2 ms TLS Handshake 5 ms Server Processing 4 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback