Skip to content
https://mollie.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
4 PASS 5 REVIEW
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

B
URL Variants
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.mollie.com/
200https://mollie.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://mollie.com/ https://mollie.com:443/

Consistent

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

Connection waterfall

DNS Lookup 8 ms TCP Connect 1 ms TLS Handshake 7 ms Server Processing 1.20 s Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
41 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Google Cloud CDN
REVIEW
Google Cloud CDN
Info::
Site is served via Google Cloud CDN CDN
Got: via: 1.1 google
CDN Detected: Google Cloud CDN
Provider Google Cloud CDN Evidence via: 1.1 google
A+
DNS Records
1 A records, 22 ms lookup
PASS
1 A records, 22 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.128.165.251
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
Info::
5 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: 22 ms
Got: 22 ms
A34.128.165.251
AAAA
CNAME
NSns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
TXT
count-okta-S8nBtWGG1pNtjuy5S2p29
CKO=cli_xxru34e4v4kezi7xxkdb4vn6ti
maven-domain-verification=ylhicbatys
apple-domain-verification=P6t7ibCD57Ks8ySP
docusign=ed21ba74-b9ba-4227-ad85-cfb18cb1b336
jamf-site-verification=yG3KrFNVoQ2dtqMnkks1cQ
1password-site-verification=VICI5I5G3ZFNHNZUMTFUOE7DXQ
docker-verification=be34279c-85d7-4673-9750-c256e923396f
facebook-domain-verification=stc7mgdejvo0n3wodfxlzjtbx9rejl
mixpanel-domain-verify=96ac912b-fe68-4670-9ed8-4abbfa7f4ce5
pinterest-site-verification=fe7b5c9a049f83497c3533f769c78c30
digicert-domain-verification=_zyleeisypsp0kaldv2ci3eei7w1i0z4
remote-domain-verification=20639883-6d0d-4bbd-a3be-31540b29d9b1
dtm-domain-verification=lySFENUbIP7tqJYSnorjZ92r-rDb_DcligerGlYI_Pw
google-site-verification=I3p5mTUmo64TgrFkQkFAH0eFxntdrQlRN7Nqz9plxSE
google-site-verification=YI1XhqSOrKf_Pbt1kn92EAUAnm4NEsa32ffRwCdetRE
apple-domain-verification=5ZrXdcuNFQKnXx0Ko_aSz9FbEVrYSj1W-9JYN85NRK4
h1-domain-verification=HrQEnFVtSHxi5y2MKaxGCRH5KjgqeCPmLppaZHbqpYWgu7Fa
globalsign-domain-verification=Z6VpqooFO95Z21kE24ScZqLH_1b3sgiiLYYJ6YaCLW
hubspot-domain-verification=ZmVkNDhkZDItNGMzNi00NjBlLWI3MTQtZTUwMDFlM2IyOTQ0
SPF v=spf1 ip4:81.93.166.36/31 include:_spf.google.com include:mail.zendesk.com -all
atlassian-domain-verification=YtEfelC1r3jpY1Fgm+X+JHik3soTZgNbU6ixW/1fZvGwisa38V...
postman-domain-verification=0b80cc4be8aa9d58e6d285836415c11ffc7ce3ef02305a3631b2...
CAALookup not available with standard resolver
Resolved in 22 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), 404 ms total
PASS
1 redirect(s), 404 ms total
Info::
Single redirect
Got: https://mollie.com → https://www.mollie.com/ (301)
Info::
WWW normalization redirect

https://mollie.com

352 ms · HTTP/1.1

301

https://www.mollie.com/

53 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mollie.com301352 msHTTP/1.1Mollie
2https://www.mollie.com/20053 msHTTP/1.1Mollie

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 28 URLs
PASS
robots.txt present, sitemap with 28 URLs
Info::
robots.txt is present
Got: 67 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 28 entries
Info::
Sitemap index with 28 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 67 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /

Sitemap: https://www.mollie.com/sitemap.xml
A+
Domain Intelligence
mollie.com — via Key-Systems GmbH, 22 years, 11 months old, hosted on Google Cloud
PASS
mollie.com — via Key-Systems GmbH, 22 years, 11 months old, hosted on Google Cloud
Info::
Domain registered until Aug 26, 2026 (4 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Key-Systems GmbH
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: Google Cloud
Got: AS396982
Domain expiry

72 days

August 26, 2026

SSL certificate

41 days

Issued by Google Trust Services

Domain age

22 years, 11 months

Registered August 26, 2003

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.128.165.251

Registrar

Key-Systems GmbH

Unlocked 4 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 Key-Systems GmbH
Created August 26, 2003 (22 years, 11 months ago)
Expires August 26, 2026 (4 months)
Last Updated November 27, 2025
Name Servers ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
DNSSEC Enabled
Hosting
IP Address 34.128.165.251
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: rdap (0.5s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback