Skip to content
https://mopar.eu

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
11
PASS
6
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
17
6 PASS 11 REVIEW
B
DNS Records
2 A records, 34 ms lookup
REVIEW
2 A records, 34 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 23.211.135.144, 23.211.135.149
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:e0::211:2562, 2a02:26f0:e0::211:25c2
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: www.mopar.eu.edgekey.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: 34 ms
Got: 34 ms
A23.211.135.144, 23.211.135.149
AAAA2a02:26f0:e0::211:2562, 2a02:26f0:e0::211:25c2
CNAMEwww.mopar.eu.edgekey.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 34 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.
B
Reverse DNS
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR for 23.211.135.144 does not match any cert SAN: a23-211-135-144.deploy.static.akamaitechnologies.com
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 23.211.135.149 does not match any cert SAN: a23-211-135-149.deploy.static.akamaitechnologies.com
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 2a02:26f0:e0::211:2562 does not match any cert SAN: g2a02-26f0-00e0-0000-0000-0000-0211-2562.deploy.static.akamaitechnologies.com
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 2a02:26f0:e0::211:25c2 does not match any cert SAN: g2a02-26f0-00e0-0000-0000-0000-0211-25c2.deploy.static.akamaitechnologies.com
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.
B
Multi-Resolver DNS Speed
Mean 69ms across 3 resolvers (spread 141ms)
REVIEW
Mean 69ms across 3 resolvers (spread 141ms)
Info::
Cloudflare: 18ms
Got: 18ms via 1.1.1.1:53
Info::
Google: 31ms
Got: 31ms via 8.8.8.8:53
Info::
Quad9: 159ms
Got: 159ms via 9.9.9.9:53
B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 403 Expected: 301 redirect to HTTPS

www / non-www

200https://www.mopar.eu/
https://mopar.eu/

HTTP → HTTPS

403http://www.mopar.eu/

HTTP version does not redirect to HTTPS

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

Certificate validity

53
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
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
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+
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+
Redirect Chain
0 redirect(s), 20 ms total
PASS
0 redirect(s), 20 ms total

https://www.mopar.eu

20 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.mopar.eu40320 msHTTP/1.1AkamaiGHost
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:e0::211:2562, 2a02:26f0:e0::211:25c2
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:e0::211:2562, 2a02:26f0:e0::211:25c2 Connection Reachable (1 ms)
A+
Domain Intelligence
mopar.eu — via CSC CORPORATE DOMAINS INC., hosted on Microsoft Azure
PASS
mopar.eu — via CSC CORPORATE DOMAINS INC., hosted on Microsoft Azure
Info::
Registrar: CSC CORPORATE DOMAINS INC.
Info::
Hosting: Microsoft Azure
Got: AS8069
Domain expiry

Unknown

SSL certificate

53 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8069

20.47.97.150

Registrar

CSC CORPORATE DOMAINS INC.

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Registrar CSC CORPORATE DOMAINS INC.
Name Servers dns2.cscdns.net, dns1.cscdns.net
Registrant NOT DISCLOSED!
Hosting
IP Address 20.47.97.150
ASN AS8069 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: whois (0.5s)
A+
HTTP Probe Timing
Total 69 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
53 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.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
69 ms
Total Time Total request time from DNS lookup through full response.
69 ms

Connection waterfall

DNS Lookup 53 ms TCP Connect 1 ms TLS Handshake 8 ms Server Processing 8 ms Content Transfer 0 ms
A+
Health Check Endpoint
Auth-protected health endpoint at https://www.mopar.eu/health (HTTP 403)
PASS
Auth-protected health endpoint at https://www.mopar.eu/health (HTTP 403)
Info::
Auth-protected health endpoint exposed at https://www.mopar.eu/health
Got: https://www.mopar.eu/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback