Skip to content
https://arm.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
302 Found
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

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.arm.com/
200https://arm.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://arm.com/ https://arm.com/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

83
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
1 A records, 112 ms lookup
PASS
1 A records, 112 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 217.140.110.36
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns9.arm.com, ns10.arm.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: 112 ms
Got: 112 ms
A217.140.110.36
AAAA
CNAME
NSns9.arm.com, ns10.arm.com
MX
10 arm-com.mail.protection.outlook.com
TXT
miro-verification=519a170e96753c702023321610d10cf2564c2fb6
scnv-verification=2dc0c3db9aeb6cc6cbc4d01b352a776a:304298b8f07d069b4fe822ae05fa4...
docusign=4354edae-504a-4b6b-87e6-1e4ff8faa4b4
facebook-domain-verification=p9lo864qhly23ne718q7xpx8ou5en5
google-site-verification=wAP0CMj1e4ykhDl5tvr_TRJDLTQCRu2Ssi_lN5XBdns
_globalsign-domain-verification=RW5XFgbr6HEWfe8ifSSAodFQYdy3tAqZ-Pza5nYpFu
atlassian-domain-verification=Kab7/mjw4dDUOKLoQrDFRANUr861TeImKTyMXKzs4qtnFUEpg+...
pTXUqVOFDgvKujvb2YneVrgSMs4HO2L3QY/DBptqMX0=
parallels-domain-verification=63113f27e7e54ff1b08f85e406ae405970a0957b720046d4b2...
asv=73e72696310a7c875d617954c2c2380b
google-site-verification=sFxb2VJWasr0bcA0AfiCwrxNInZ_BwXA0kQf1w9WmSI
_globalsign-domain-verification=xl_zUjAb5e-087Hw3oq00POA4DNbyJcyjKUUQtmymv
7Ms7HXWIVBFZt8rbhyvRZj1SjMLKHUGxpBcwH2lfQV8=
loom-site-verification=0c5ca6a1e0644cad80e3dabbae38bce3
remarkable-domain-verification=0e104644-0823-47c1-8207-e6f8cfc4b56d
MS=ms75314990
e880bd87-df0f-4092-a5ec-5d2355aadfbb
t6keBVEiT94PQwcYb3UwyLUpkWVpEfUR+GHpHBd6L24=
docusign=3378549e-e22d-4ebb-a1fc-13cd3e7657cd
6lGRnuRk8kC0MPI/1xxIjEKbcbRHL5yBXKoXofWbiXQ=
SPF v=spf1 include:_spf-a.arm.com include:_spf-b.arm.com include:_spf-c.arm.com -all
jamf-site-verification=N8SpeAd-0sZd-eq7yo86tw
Validity-Domain-Verification=+fvuyK4xGf8IYtdYiPEHhu+B90A=
7hH07yiIUzNg+lhbIbS2I+qoyXam+XYjZQphd30oy2s=
00de0000000l5gtmak
mongodb-site-verification=xXRygrrDunBRlVKK2gclJFnFrCmNa7vJ
arm.com Globalsign validation
wZESOmeviH35RYkJm+jmvdFq3S4s8LaNfUvlocmmFcg=
75mg2wb15tKXyadX7ubMPLg5fJz9kISG9XOX1+1aTMA=
Dynatrace-site-verification=83ffa8fa-73e2-4d46-878a-734e3bbfbc8c__tuevt2jng9172h...
docker-verification=44a6692b-6e77-44fd-8701-071d06f9f319
google-site-verification=tHuC5YTqt9gYnORmLQokkO-KBiiM86U1qvCrTb2Zh_w
docusign=1b941d60-18db-4bc0-893a-9f050c6ff220
arm.com.00DE0000000L5GtMAK.live.siteforce.com
apple-domain-verification=BSBEa0gMuEQAMKLR
atlassian-sending-domain-verification=dbd0283e-6213-4e44-a9e0-d105d0798424
MS=ms99651240
CAALookup not available with standard resolver
Resolved in 112 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), 803 ms total
PASS
1 redirect(s), 803 ms total
Info::
Single redirect
Got: https://arm.com → https://www.arm.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://arm.com
Info::
Redirect overhead: 803 ms total
Got: 803 ms

https://arm.com

695 ms · HTTP/1.1

302

https://www.arm.com/

108 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://arm.com302695 msHTTP/1.1
2https://www.arm.com/200108 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
Crawlability
robots.txt present, sitemap with 9 URLs
PASS
robots.txt present, sitemap with 9 URLs
Info::
robots.txt is present
Got: 2109 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 9 entries
Info::
Sitemap index with 9 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2109 B Sitemaps referenced 1 User-agents ChatGPT-User, Sogou, Amazonbot, Applebot, PerplexityBot, AhrefsBot, YandexBot, SemrushBot, SEOkicks, CoveoEnterpriseSearch, CCBot, Google-Extended, Bytespider, Qwantify/Bleriot, Claude-web, Bingbot, *, MegaIndex.ru, DotBot, MJ12bot, anthropic-ai, GPTBot, ClaudeBot Blocking No — crawling allowed
# ============================

# robots.txt for www.arm.com

# ============================


# ----------------------------

# ALLOW: Trusted AI/LLM Crawlers for Training & Indexing

# ----------------------------


User-agent: anthropic-ai

Allow: /llms.txt


User-agent: GPTBot

Allow: /llms.txt


User-agent: ClaudeBot

Allow: /llms.txt


User-agent: Claude-web

Allow: /llms.txt


User-agent: CCBot

Allow: /llms.txt


User-agent: Google-Extended

Allow: /llms.txt


User-agent: Amazonbot

Allow: /llms.txt


User-agent: Applebot

Allow: /llms.txt


User-agent: Bingbot

Allow: /llms.txt


User-agent: ChatGPT-User

Allow: /llms.txt


User-agent: Bytespider

Allow: /llms.txt


User-agent: PerplexityBot

Allow: /llms.txt


User-agent: Sogou

Allow: /llms.txt


Sitemap: https://www.arm.com/sitemap_index.xml


# ----------------------------

# Internal Search Bot - Limited Access

# ----------------------------

User-agent: CoveoEnterpriseSearch

Allow: /news/20*


User-agent: *

Disallow: /coveo/


# ----------------------------

# BLOCK: Crawlers with Low Value or High Server Load

# ----------------------------

User-agent: AhrefsBot

Disallow: /


User-agent: YandexBot

Disallow: /


User-agent: MegaIndex.ru

Disallow: /


User-agent: SemrushBot

Disallow: /


User-agent: Qwantify/Bleriot

Disallow: /


User-agent: DotBot

Disallow: /


User-agent: MJ12bot

Disallow: /


User-agent: SEOkicks

Disallow: /


# ----------------------------

# GENERAL RULES - Internal/Private Paths

# ----------------------------

User-agent: *


# Backend or dev/testing paths

Disallow: /assets/fonts/

Disallow: /assets/Fonts/

Disallow: /includes/

Disallow: /phpscripts/

Disallow: /shouldremainempty/

Disallow: /xml/

Disallow: /zh/includes/

Disallow: /zh/shouldremainempty/

Disallow: /zh/xml/

Disallow: /about/newsroom


# Block legacy trademark-related assets

Disallow: /-/media/global/company/policies/trademarks/incorrect-logo/


# Block thank-you pages or soft redirects

Disallow: /*-ty$


# Block internal site search

Disallow: /search*

Disallow: /Search*
A+
Domain Intelligence
arm.com — via Nom-iq Ltd. dba COM LAUDE, 31 years, 7 months old, hosted on ARM-AS, GB
PASS
arm.com — via Nom-iq Ltd. dba COM LAUDE, 31 years, 7 months old, hosted on ARM-AS, GB
Info::
Domain registered until Feb 8, 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: Nom-iq Ltd. dba COM LAUDE
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: ARM-AS, GB
Got: AS28939
Domain expiry

237 days

February 8, 2027

SSL certificate

83 days

Issued by GlobalSign nv-sa

Domain age

31 years, 7 months

Registered February 7, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

ARM-AS, GB

ASN AS28939

217.140.110.36

Registrar

Nom-iq Ltd. dba COM LAUDE

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 Nom-iq Ltd. dba COM LAUDE
Created February 7, 1995 (31 years, 7 months ago)
Expires February 8, 2027 (9 months)
Last Updated February 3, 2026
Name Servers ns10.arm.com, ns9.arm.com
DNSSEC Not enabled
Hosting
IP Address 217.140.110.36
ASN AS28939 (ARM-AS, GB)
Provider ARM-AS, GB
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 40 ms TCP Connect 153 ms TLS Handshake 309 ms Server Processing 152 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