Skip to content
https://nielsen.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://nielsen.com/ https://nielsen.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • 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
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 14 ms lookup
PASS
1 A records, 14 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.0.66.96
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: pdns1.ultradns.net, pdns2.ultradns.net, pdns3.ultradns.org, pdns4.ultradns.org, pdns5.ultradns.info, pdns6.ultradns.co.uk
Info::
5 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: 14 ms
Got: 14 ms
A192.0.66.96
AAAA
CNAME
NSpdns1.ultradns.net, pdns2.ultradns.net, pdns3.ultradns.org, pdns4.ultradns.org, pdns5.ultradns.info, pdns6.ultradns.co.uk
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
spf2.0/pra
MS=ms41051260
MS=ms67552876
_ai81x2u5stppdkyre8n0ezt5ky1t4lt
SPF v=spf1 redirect=nielsenmedia.com
78bbee88-ff35-4ebd-a89c-c171623a2556
asv=bf2e463d186d760daa4dac04f2189363
chariot=chariot+nielsen@praetorian.com
apple-domain-verification=JTibV8tKhqrsFjn5
S++U9DTmPuWS35PmOtd+b9EGXReFRPlH3OCLbosxcd4=
docusign=eff616df-1c79-4f17-a483-41df197156e0
amazonses:0JosrlclByQF0TUsPNy0SQef9qg/hdQRAXwkGMEKxUA=
amazonses:PGjwQCzzs3Wm+ONWo5DNcDbTKPBaomU4C+g+w8bQ0Cc=
amazonses:RU3KDh1Q6flY8zP+pA0WOA8kuCaXCFdSoNIdQBySLYQ=
amazonses:prkq66HtyEY2olarwkuQTxOKmVpexTvKSKZD0nTrZsw=
amazonses:CMjF0nhMIlOStaYBRZZf+5dETxEYbvqkyw6bo3tG62U=
miro-verification=bd31f86ea27054eddbcf39ef767cce5163f1d7dd
cursor-domain-verification-nrtyzf=yn7HXR3200uZTbCpwUOh2WpNk
facebook-domain-verification=sl8du0ke9guurybwg45jxj8i479ev7
smartsheet-site-validation=vFfZpWmTE4YfhFSxtnG5j3_p_hu4k_xO
workplace-domain-verification=UFAkrwf7ECD95XHT8EBiP1aQoYsZPu
onetrust-domain-verification=8c659e5cd0434b48af1ee2a02d71471c
anthropic-domain-verification-xea344=7JYUkKzKsua4Uwb8UBXKT88Vu
vmware-cloud-verification-e7e740f3-1587-48ca-a362-dfb52b02dab2
google-site-verification=bxXOriWggTqH_8xPx5gPdOwac9leSuqcQludAHOxJE0
liveramp-site-verification=ACjlvkmxMUhaIkPSnxfs-XEfK7bUAz0a9NGGrnYjGfo
_globalsign-domain-verification=uqDQCq1dOLC9lyzN68Grz66P1qpMXrUgu-Q111CVVw
atlassian-sending-domain-verification=8c150d6d-0537-4aaf-80e9-a9dd8ca01648
pardot31782=b80a14ec11c49bb8307f78a6de296a7fd52bf73edbe8b1148c699eba6d6fc88e
pardot407042=326c335e144c4c389b1fd392bfce3fe651f86670057bbce87a5cbba848477c5a
pardot881703=bda145131aa75cc8b4ffbcd3a03b6030184b13efe5c428318ae54a4fd575a548
pardot_85462_*=3d08aa457edc0a6d5f8402a9f27e97be967bd899ec40de3ef5517a10c3a7bad0
Dynatrace-site-verification=e8499418-763b-4e07-a2a9-630887963898__2lre76d6k2cspk...
adobe-idp-site-verification=d4250894cee614bbe020fa949280b0ad410c6b2930ba4383f465...
cisco-ci-domain-verification=4cb7d8a43966e27101c7b4a6f465153af246a51d22896fb1077...
cisco-ci-domain-verification=6942166472e691ef8e55cb4759b596597527a28b064e4fc2592...
atlassian-domain-verification=sTb4hFWtIi5V/G7/I/PG5eYIA95YUMrC+ucuxckH99NzjiBo/5...
wrike-verification=Mjk1ODE5OTpkM2Y4Y2NmZDY3YTI5YWQ3ZGExMjJhNmRmNjRlYjBjMWI1YmQ3Y...
CAALookup not available with standard resolver
Resolved in 14 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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
1 redirect(s), 23 ms total
PASS
1 redirect(s), 23 ms total
Info::
Single redirect
Got: https://nielsen.com → https://www.nielsen.com/ (301)
Info::
WWW normalization redirect

https://nielsen.com

10 ms · HTTP/1.1

301

https://www.nielsen.com/

13 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nielsen.com30110 msHTTP/1.1nginx
2https://www.nielsen.com/20013 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 21 URLs
PASS
robots.txt present, sitemap with 21 URLs
Info::
robots.txt is present
Got: 205 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 21 entries
Info::
Sitemap index with 21 child sitemaps
Info::
robots.txt references sitemap
A+
Domain Intelligence
nielsen.com — via MarkMonitor Inc., 35 years, 5 months old, hosted on WordPress.com (Automattic)
PASS
nielsen.com — via MarkMonitor Inc., 35 years, 5 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until May 9, 2027 (1 years 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: WordPress.com (Automattic)
Got: AS2635
Domain expiry

327 days

May 9, 2027

SSL certificate

82 days

Issued by Let's Encrypt

Domain age

35 years, 5 months

Registered May 8, 1991

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.66.96

Registrar

MarkMonitor Inc.

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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created May 8, 1991 (35 years, 5 months ago)
Expires May 9, 2027 (1 years)
Last Updated April 7, 2026
Name Servers udns1.ultradns.net, udns2.ultradns.net
DNSSEC Not enabled
Hosting
IP Address 192.0.66.96
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: rdap (0.2s)

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 11 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.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
11 ms
Total Time Total request time from DNS lookup through full response.
11 ms

Connection waterfall

DNS Lookup 4 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 2 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