Skip to content
https://www.accenture.com/de-de

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
6
PASS
11
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
11 PASS 6 REVIEW
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.
B
Reverse DNS
0/12 IPs match cert SAN
REVIEW
0/12 IPs match cert SAN
Info::
PTR for 13.224.83.117 does not match any cert SAN: server-13-224-83-117.mad53.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 13.224.83.83 does not match any cert SAN: server-13-224-83-83.mad53.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 13.224.83.19 does not match any cert SAN: server-13-224-83-19.mad53.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 13.224.83.82 does not match any cert SAN: server-13-224-83-82.mad53.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR lookup failed for 2600:9000:2131:1a00:d:5159:5a00:93a1: lookup 2600:9000:2131:1a00:d:5159:5a00:93a1: 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 2600:9000:2131:ce00:d:5159:5a00:93a1: lookup 2600:9000:2131:ce00:d:5159:5a00:93a1: 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 2600:9000:2131:a400:d:5159:5a00:93a1: lookup 2600:9000:2131:a400:d:5159:5a00:93a1: 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 2600:9000:2131:3e00:d:5159:5a00:93a1: lookup 2600:9000:2131:3e00:d:5159:5a00:93a1: 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 2600:9000:2131:ac00:d:5159:5a00:93a1: lookup 2600:9000:2131:ac00:d:5159:5a00:93a1: 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 2600:9000:2131:d000:d:5159:5a00:93a1: lookup 2600:9000:2131:d000:d:5159:5a00:93a1: 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 2600:9000:2131:f200:d:5159:5a00:93a1: lookup 2600:9000:2131:f200:d:5159:5a00:93a1: 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 2600:9000:2131:200:d:5159:5a00:93a1: lookup 2600:9000:2131:200:d:5159:5a00:93a1: 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
Domain Intelligence
accenture.com — via CSC Corporate Domains, Inc., 26 years, 4 months old, hosted on ACCENTURE - Accenture LLP, US
REVIEW
accenture.com — via CSC Corporate Domains, Inc., 26 years, 4 months old, hosted on ACCENTURE - Accenture LLP, US
Critical::
Domain expires in 9 days
This domain expires on August 29, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Got: Expires Aug 29, 2026
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

3 days

August 29, 2026

SSL certificate

192 days

Issued by DigiCert Inc

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
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • 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, 2026 (9 days)
Last Updated May 15, 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.9s)

This domain expires on August 29, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
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.
A
DNS Records
4 A records, 56 ms lookup
PASS
4 A records, 56 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 13.224.83.117, 13.224.83.83, 13.224.83.19, 13.224.83.82
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:2131:1a00:d:5159:5a00:93a1, 2600:9000:2131:ce00:d:5159:5a00:93a1, 2600:9000:2131:a400:d:5159:5a00:93a1, 2600:9000:2131:3e00:d:5159:5a00:93a1, 2600:9000:2131:ac00:d:5159:5a00:93a1, 2600:9000:2131:d000:d:5159:5a00:93a1, 2600:9000:2131:f200:d:5159:5a00:93a1, 2600:9000:2131:200:d:5159:5a00:93a1
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: 4229prod2cf.r53cioaccenturecloud.net
Info::
4 nameserver(s) configured
Got: ns-1679.awsdns-17.co.uk, ns-33.awsdns-04.com, ns-745.awsdns-29.net, ns-1488.awsdns-58.org
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: 56 ms
Got: 56 ms
A13.224.83.117, 13.224.83.83, 13.224.83.19, 13.224.83.82
AAAA2600:9000:2131:1a00:d:5159:5a00:93a1, 2600:9000:2131:ce00:d:5159:5a00:93a1, 2600:9000:2131:a400:d:5159:5a00:93a1, 2600:9000:2131:3e00:d:5159:5a00:93a1, 2600:9000:2131:ac00:d:5159:5a00:93a1, 2600:9000:2131:d000:d:5159:5a00:93a1, 2600:9000:2131:f200:d:5159:5a00:93a1, 2600:9000:2131:200:d:5159:5a00:93a1
CNAME4229prod2cf.r53cioaccenturecloud.net
NSns-1679.awsdns-17.co.uk, ns-33.awsdns-04.com, ns-745.awsdns-29.net, ns-1488.awsdns-58.org
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 56 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)

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 31ms across 3 resolvers (spread 29ms)
PASS
Mean 31ms across 3 resolvers (spread 29ms)
Info::
Quad9: 15ms
Got: 15ms via 9.9.9.9:53
Info::
Google: 36ms
Got: 36ms via 8.8.8.8:53
Info::
Cloudflare: 44ms
Got: 44ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.accenture.com/de-de

https://www.accenture.com/de-de

26 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.accenture.com/de-de20026 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2600:9000:2131:1a00:d:5159:5a00:93a1, 2600:9000:2131:ce00:d:5159:5a00:93a1, 2600:9000:2131:a400:d:5159:5a00:93a1, 2600:9000:2131:3e00:d:5159:5a00:93a1, 2600:9000:2131:ac00:d:5159:5a00:93a1, 2600:9000:2131:d000:d:5159:5a00:93a1, 2600:9000:2131:f200:d:5159:5a00:93a1, 2600:9000:2131:200:d:5159:5a00:93a1
Got: 1 ms connect
IPv6 Ready
AAAA Records 2600:9000:2131:1a00:d:5159:5a00:93a1, 2600:9000:2131:ce00:d:5159:5a00:93a1, 2600:9000:2131:a400:d:5159:5a00:93a1, 2600:9000:2131:3e00:d:5159:5a00:93a1, 2600:9000:2131:ac00:d:5159:5a00:93a1, 2600:9000:2131:d000:d:5159:5a00:93a1, 2600:9000:2131:f200:d:5159:5a00:93a1, 2600:9000:2131:200:d:5159:5a00:93a1 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 109 URLs
PASS
robots.txt present, sitemap with 109 URLs
Info::
robots.txt is present
Got: 836 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 109 entries
Info::
Sitemap index with 109 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 836 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: */Careers/Registration

Disallow: */Careers/Form

Disallow: */Careers/Profiles

Disallow: */error/

Disallow: */loginpage

Disallow: */sitecore/

Disallow: */BucketContent

Disallow: */RedesignBucket

Disallow: */core/

Disallow: */?sc_lang

Disallow: */secure/

Disallow: */clients/

Disallow: */client/

Disallow: */a-com-no-follow-no-index/

Disallow: */_acnmedia/

Disallow: */_globalreferences/

Disallow: /us-en/careers/admin/careersxmlresult

Disallow: /*/header/global-header/

Disallow: /*.nocache.html

Disallow: */content/acom/

Disallow: /*tlaAppCB

Disallow: */careers/jobsearch?

Disallow: */search/ai-search

Disallow: */search/results

Disallow: /*WHB

Disallow: /*Channel

Disallow: /*channel 

Disallow: /*target_id

Disallow: /*utm_source

sitemap: https://www.accenture.com/sitemap-index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 109 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.accenture.com/de-de
301https://accenture.com/de-de

Preferred variant: www

Trailing Slash

301https://www.accenture.com/de-de/
200https://www.accenture.com/de-de

HTTP → HTTPS

301http://www.accenture.com/de-de → https://www.accenture.com/de-de

Consistent

A+
HTTP Probe Timing
Total 119 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
58 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.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
119 ms
Total Time Total request time from DNS lookup through full response.
120 ms

Connection waterfall

DNS Lookup 58 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 58 ms Content Transfer 1 ms
A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: MAD53-P6)
Got: x-amz-cf-id: VXrLb8dBrKeArnjg6I2UD8YadzqS4EH-dEZdyjfISptNQ6AfcWvc-A==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: VXrLb8dBrKeArnjg6I2UD8YadzqS4EH-dEZdyjfISptNQ6AfcWvc-A==
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 3 header(s)
Got: age=1838, x-cache=Miss from cloudfront, x-served-by=cache-par-lfpb1150027-PAR
A+
Health Check Endpoint
Health endpoint at https://www.accenture.com/health (HTTP 200)
PASS
Health endpoint at https://www.accenture.com/health (HTTP 200)
Info::
Public health endpoint at https://www.accenture.com/health
Got: https://www.accenture.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback