Skip to content
https://nxp.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
6 PASS 2 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
TLS Certificate Expiry & Recommendations
224 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

224
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
2 A records, 32 ms lookup
PASS
2 A records, 32 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 35.161.17.93, 52.43.212.231
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1.nxp.net, ns2.nxp.net, ns3.nxp.net, ns4.nxp.net
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: 32 ms
Got: 32 ms
A35.161.17.93, 52.43.212.231
AAAA
CNAME
NSns1.nxp.net, ns2.nxp.net, ns3.nxp.net, ns4.nxp.net
MX
5 nxp-com.mail.protection.outlook.com
TXT
0bc7076b4dcb6a4b46541c9d6ba850b2e2bb69b9e22ed46d8f06524c054b948a
G3M3YGHgS/Ux/Z+sgz8aMxMec0Gigs3LPCUa/44saI24GoMeyilF5D9LqfGuV9zSX0rNyHLMy/6E/qws...
autodesk-domain-verification=SBWvoedG681jwdHhv6Qn
cisco-ci-domain-verification=e2a8bb50a515ed38e3f513c63d7a7c8790d2aa4a9aaf9316401...
google-site-verification=--4xe5qGlChX4AbUTCi3R0rnrBjxS5bGaPSXv-jaulY
logmein-verification-code=3e95c8df-7c28-44a9-a6cc-6a92894432ea
miro-verification=60331d923bccaeea9f25956868d156b32b2da283
onetrust-domain-verification=1b7b3faf25a74e638137a6db05efa56d
onetrust-domain-verification=b7db4113c9ac40a0a01239a044a4c1f2
twilio-domain-verification=be6cbcfc8284928c51f3a22efd778150
SPF v=spf1 include:spf.nxp.com include:spf.protection.outlook.com -all
CAALookup not available with standard resolver
Resolved in 32 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
1 redirect(s), 114 ms total
PASS
1 redirect(s), 114 ms total
Info::
Single redirect
Got: https://nxp.com → https://www.nxp.com:443/ (301)
Info::
WWW normalization redirect

https://nxp.com

85 ms · HTTP/1.1

301

https://www.nxp.com:443/

28 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nxp.com30185 msHTTP/1.1awselb/2.0
2https://www.nxp.com:443/20028 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 665 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
Sitemap index with 4 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 665 B Sitemaps referenced 1 User-agents *, Baiduspider Blocking No — crawling allowed
#
# robots.txt for http://www.w3.org/
#
# $Id: robots.txt,v 1.22 2002/04/18 20:23:04 ted Exp $
#

User-agent: *
Disallow: /files/benefits
Disallow: /files/global_support_files
Disallow: /search
Disallow: /ftfevent
Disallow: /about/about-nxp/about-nxp/benefits
Disallow: /company/our-company/about-nxp/benefits

#Baiduspider
User-agent: Baiduspider
Disallow: /files/benefits
Disallow: /files/global_support_files
Disallow: /search
Disallow: /ftfevent
Disallow: /about/about-nxp/about-nxp/benefits
Disallow: /company/our-company/about-nxp/benefits
Disallow: /company/about-nxp/newsroom/nxp-statement-on-ukraine:NXP-STATEMENT

Sitemap: https://www.nxp.com/sitemap.xml

A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

404https://www.nxp.com/
200https://nxp.com/

HTTP → HTTPS

302http://nxp.com/ https://nxp.com:443/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
nxp.com — via CSC Corporate Domains, Inc., 29 years, 6 months old, hosted on AWS
PASS
nxp.com — via CSC Corporate Domains, Inc., 29 years, 6 months old, hosted on AWS
Info::
Domain registered until Mar 5, 2027 (10 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

262 days

March 5, 2027

SSL certificate

224 days

Issued by Amazon

Domain age

29 years, 6 months

Registered March 4, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

35.161.17.93

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 March 4, 1997 (29 years, 6 months ago)
Expires March 5, 2027 (10 months)
Last Updated March 1, 2026
Name Servers ns1.nxp.net, ns2.nxp.net, ns3.nxp.net, ns4.nxp.net
DNSSEC Not enabled
Hosting
IP Address 35.161.17.93
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
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 77 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
7 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
23 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
24 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
78 ms
Total Time Total request time from DNS lookup through full response.
78 ms

Connection waterfall

DNS Lookup 7 ms TCP Connect 23 ms TLS Handshake 24 ms Server Processing 24 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