Skip to content
https://newsroom.accenture.com/news/2025/accenture-and-schaeffler-pave-the-way-for-industrial-humanoid-robots-with-nvidia-and-microsoft-technologies

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
17
9 PASS 7 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2a06:98c1:3105::6812:23e1, 2606:4700:4400::ac40:981f
Info::
IPv6 connection error
Got: dial tcp6 [2a06:98c1:3105::6812:23e1]:443: connect: no route to host
IPv6 Misconfigured
AAAA Records 2a06:98c1:3105::6812:23e1, 2606:4700:4400::ac40:981f Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

B
DNS Records
2 A records, 21 ms lookup
REVIEW
2 A records, 21 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.35.225, 172.64.152.31
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3105::6812:23e1, 2606:4700:4400::ac40:981f
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: 254599.184452-prd.accenture.cloud.cdn.cloudflare.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 21 ms
Got: 21 ms
A104.18.35.225, 172.64.152.31
AAAA2a06:98c1:3105::6812:23e1, 2606:4700:4400::ac40:981f
CNAME254599.184452-prd.accenture.cloud.cdn.cloudflare.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 21 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 104.18.35.225: lookup 104.18.35.225: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 172.64.152.31: lookup 172.64.152.31: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2a06:98c1:3105::6812:23e1: lookup 2a06:98c1:3105::6812:23e1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:4400::ac40:981f: lookup 2606:4700:4400::ac40:981f: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
TLS Certificate Expiry & Recommendations
80 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Multi-Resolver DNS Speed
Mean 8ms across 3 resolvers (spread 10ms)
PASS
Mean 8ms across 3 resolvers (spread 10ms)
Info::
Cloudflare: 2ms
Got: 2ms via 1.1.1.1:53
Info::
Quad9: 11ms
Got: 11ms via 9.9.9.9:53
Info::
Google: 12ms
Got: 12ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://newsroom.accenture.com/news/2025/accenture-and-schaeffler-pave-the-way-for-industrial-humanoid-robots-with-nvidia-and-microsoft-technologies

https://newsroom.accenture.com/news/2025...

72 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://newsroom.accenture.com/news/2025...20072 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 3667 URLs
PASS
robots.txt present, sitemap with 3667 URLs
Info::
robots.txt is present
Got: 86 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3667 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 86 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /archive

Sitemap: https://newsroom.accenture.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 3667 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

https://www.newsroom.accenture.com/news/2025/accenture-and-schaeffler-pave-the-way-for-industrial-humanoid-robots-with-nvidia-and-microsoft-technologies
200https://newsroom.accenture.com/news/2025/accenture-and-schaeffler-pave-the-way-for-industrial-humanoid-robots-with-nvidia-and-microsoft-technologies

Trailing Slash

404https://newsroom.accenture.com/news/2025/accenture-and-schaeffler-pave-the-way-for-industrial-humanoid-robots-with-nvidia-and-microsoft-technologies/
200https://newsroom.accenture.com/news/2025/accenture-and-schaeffler-pave-the-way-for-industrial-humanoid-robots-with-nvidia-and-microsoft-technologies

HTTP → HTTPS

301http://newsroom.accenture.com/news/2025/accenture-and-schaeffler-pave-the-way-for-industrial-humanoid-robots-with-nvidia-and-microsoft-technologies → https://newsroom.accenture.com/news/2025/accenture-and-schaeffler-pave-the-way-for-industrial-humanoid-robots-with-nvidia-and-microsoft-technologies

Consistent

A+
Domain Intelligence
accenture.com — via CSC Corporate Domains, Inc., 26 years, 4 months old, hosted on ACCENTURE - Accenture LLP, US
PASS
accenture.com — via CSC Corporate Domains, Inc., 26 years, 4 months old, hosted on ACCENTURE - Accenture LLP, US
Info::
Domain registered until Aug 29, 2027 (1 years remaining)
Info::
DNSSEC is enabled
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: ACCENTURE - Accenture LLP, US
Got: AS3573
Domain expiry

360 days

August 29, 2027

SSL certificate

80 days

Issued by Google Trust Services

Domain age

26 years, 4 months

Registered August 29, 2000

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

ACCENTURE - Accenture LLP, US

ASN AS3573

170.248.56.19

Registrar

CSC Corporate Domains, Inc.

Unlocked 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created August 29, 2000 (26 years, 4 months ago)
Expires August 29, 2027 (1 years)
Last Updated August 25, 2026
Name Servers amrns1501.accenture.com, apans3501.accenture.com, cfans1001.accenture.com, cfans1002.accenture.com, emens3501.accenture.com
DNSSEC Enabled
Hosting
IP Address 170.248.56.19
ASN AS3573 (ACCENTURE - Accenture LLP, US)
Provider ACCENTURE - Accenture LLP, US
Data source: rdap (0.8s)

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 202 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.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
12 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
202 ms
Total Time Total request time from DNS lookup through full response.
202 ms

Connection waterfall

DNS Lookup 7 ms TCP Connect 1 ms TLS Handshake 12 ms Server Processing 182 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: GRU)
Got: cf-ray: a34cb5fedeba6282-GRU
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a34cb5fedeba6282-GRU
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 4 header(s)
Got: cf-cache-status=DYNAMIC, x-cache=Hit from cloudfront, x-cache-hits=0, 0, x-served-by=cache-iad-kiad7000156-IAD, cache-iad-kcgs7200050-IAD
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback