carparts.com is a live website, registered in 1999, served from Frankfurt am Main, Germany. It has a valid HTTPS certificate, 0 of 6 common security headers, 1 tracking script.
What is carparts.com about?
The words appearing most often on the homepage, excluding common filler, are
a rough indication of subject matter rather than a description of the business:
- carparts ×2
- investor ×2
Does carparts.com publish the usual trust pages?
All four of the pages a established business normally publishes were found:
about, contact, privacy and terms.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does carparts.com compare with other domains analysed here?
Measured against the 77 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.
| Response time | Faster than 47% of them (median 496ms) |
|---|---|
| Security headers | More than 0% of them |
| Domain age | Older than 68% of them |
Related domains in this index
Analysed domains sharing the same network (AS16509 Amazon.com, Inc.):
Sharing a network means sharing a host or CDN. It implies nothing about a
relationship between the sites themselves.
Other analysed domains served from the same country:
When was carparts.com registered?
carparts.com was registered on 19 March 1999, which makes it about 27 years old.
A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.
The registrar of record is GoDaddy.com, LLC.
Registration runs until 19 March 2027.
The domain carries 4 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 19 March 1999 |
|---|---|
| Expires | 19 March 2027 |
| Registrar | GoDaddy.com, LLC |
| Registry status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
Where is carparts.com hosted?
The first address resolves to infrastructure in Frankfurt am Main, Germany.
The network is operated by AWS CloudFront (GLOBAL) (AS16509 Amazon.com, Inc.).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is carparts.com running on?
No platform, framework or analytics fingerprints were found in the homepage markup of carparts.com. That usually means hand-written HTML, an uncommon stack, or a page assembled entirely at the edge.
No recognisable platform, framework or analytics fingerprints were found in the homepage markup.
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 522ms to first byte this response is unremarkable for a homepage measured from a single European location.
At 6KB the HTML is unusually small, which typically means the page builds itself client-side after load.
The HTML is compressed with gzip.
| Server header | AkamaiNetStorage |
|---|---|
| Compression | gzip |
| Page size | 5,680 bytes |
| Declared language | en |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is only 8 characters, which is short enough that it probably is not describing the page so much as naming it.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
All 1 images on the homepage have alt attributes.
| Title | Geo Page (8 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | We're sorry. (1 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 1 H2s, 1 images (0 without alt text) |
Is carparts.com served over a valid certificate?
The HTTPS certificate is issued by Amazon and is
valid until 2027-02-18, which is 136 days from the date of this check. It covers
2 hostnames.
- *.carparts.com
- carparts.com
The certificate has 136 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Which security headers does it set?
None of the 6 headers checked are set. That is the default state of most servers rather than evidence of a problem, but it means the browser is given no instructions it could otherwise act on.
Without HSTS, a browser that has never visited before will try HTTP first, which is the window a network attacker needs.
With no Content Security Policy, any script that reaches the page — including one injected through a compromised third-party dependency — runs with full access to it.
| Header | Set | Value |
|---|---|---|
| HSTS | no | — |
| Content Security Policy | no | — |
| X-Content-Type-Options | no | — |
| X-Frame-Options | no | — |
| Referrer-Policy | no | — |
| Permissions-Policy | no | — |
How is DNS configured for carparts.com?
| IP addresses | 99.84.152.62, 99.84.152.17, 99.84.152.108, 99.84.152.43 |
|---|---|
| Reverse DNS | server-99-84-152-62.fra56.r.cloudfront.net, server-99-84-152-17.fra56.r.cloudfront.net |
| Name servers | ns-1155.awsdns-16.org, ns-1655.awsdns-14.co.uk, ns-492.awsdns-61.com, ns-595.awsdns-10.net |
| Mail (MX) | carparts-com.mail.eo.outlook.com (pri 0) |
| SPF | v=spf1 include:spf.protection.outlook.com include:spf.dynect.net include:spf.us.exclaimer.net include:spf.extole.io include:spf.mandrillapp.com +ip4:45.33.207.0/24 +ip4:66.179.44.117 +ip4:130.250.130.15 +ip4:67.217.236.34 +ip4:23.21.109.197 +ip4:23.21.109.212 ip4:168.245.12.13 ip4:147.160.167.0/26 -all |
| TXT records | 22 |
carparts.com resolves to 4 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 1 exchanger.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to server-99-84-152-62.fra56.r.cloudfront.net, server-99-84-152-17.fra56.r.cloudfront.net, which usually names the hosting provider.
Who runs DNS and mail for carparts.com?
DNS is operated by Amazon Route 53 rather than self-hosted name servers.
Mail is handled by Microsoft 365.
No AAAA records are published, so the site is reachable over IPv4 only.
What else is worth noting about carparts.com?
1 of 1 externally hosted scripts carry no subresource integrity hash. If one of those hosts were compromised, the replacement script would run with full access to the page.
Can carparts.com be spoofed in email?
DMARC is published with p=none, which monitors but does not act. Forged mail is still delivered; the owner just gets reports about it.
No CAA records are published, so any certificate authority may issue a certificate for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What does robots.txt allow?
No robots.txt was served. Crawlers treat a missing file as permission to crawl
everything, so this is an open crawl policy by default rather than a blocked one.
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
What does carparts.com load from third parties?
The homepage pulls resources from 3 third-party hosts (carpartscom3278501z.btttag.com, connect.facebook.net, fonts.googleapis.com). Each one sees the visitor IP and user agent on every page load.
No cookies are set on first load.
Does carparts.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both carparts.com and www.carparts.com answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.
How easily can carparts.com be crawled?
No readable sitemap was found, so crawlers have to discover every page by following links.
A deliberately invalid URL returns HTTP 200 rather than 404. That is a soft 404: every mistyped or stale link becomes an indexable page, which inflates the site with duplicates.
What tracking does carparts.com run?
1 tracking script detected: Meta Pixel.
No consent management platform was detected alongside them. Where GDPR or the ePrivacy Directive applies, analytics and advertising scripts generally need consent before they load.
How does carparts.com look when shared?
All five social preview tags are present, so links shared to social platforms and chat apps will render with a title, description and image.
How are images, fonts and scripts handled?
1 image on the homepage, 0 of them lazy-loaded (0%).
All image references use JPEG, PNG or GIF. WebP or AVIF typically cut image weight substantially at the same visual quality.
No srcset attributes are used, so every device is served the same image size regardless of screen.
Fonts are loaded from Google Fonts, which means every page view also contacts Google. Self-hosting removes that dependency.
The page pulls 3 external stylesheets and 2 external scripts, with 2 carrying defer or async.
No preconnect hints are declared despite third-party scripts being present, so each new origin pays a full connection setup before it can deliver anything.
Is carparts.com accessible and current?
The page uses 0 landmark elements and 0 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index carparts.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
No canonical URL is declared, which leaves duplicate addresses of this page to be resolved by the search engine.
The homepage carries 2 internal and 0 external links across 0 outside hosts.
Visible text is only 2.5% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is carparts.com delivered?
No Cache-Control header is sent for the HTML, so caching behaviour is left to browser defaults.
No favicon is declared in the markup.
Frequently asked questions
Does carparts.com set the usual HTTP security headers?
It sets 0 of 6. The ones not present are: HSTS, Content Security Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
Does carparts.com allow AI crawlers?
No robots.txt is served, so nothing is disallowed and AI crawlers are free to read the site.
Where does this data come from?
Every figure was measured by our own server on 5 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own carparts.com and want this page removed.
Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 5 October 2026.
Analyse another domain →