Skip to content
https://freepik.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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
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
TLS Certificate Expiry & Recommendations
50 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

50
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
A+
DNS Records
1 A records, 84 ms lookup
PASS
1 A records, 84 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.160.205.140
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: ns15.dnsmadeeasy.com, ns14.dnsmadeeasy.com, ns12.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns11.dnsmadeeasy.com, ns10.dnsmadeeasy.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: 84 ms
Got: 84 ms
A34.160.205.140
AAAA
CNAME
NSns15.dnsmadeeasy.com, ns14.dnsmadeeasy.com, ns12.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns11.dnsmadeeasy.com, ns10.dnsmadeeasy.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
SFMC-vQ5QyjExDSQu24r4RlCGroMlhYWHUgclfZElbG7G
google-site-verification=up95Hf5DvSE8rnnt-NRyuBvu67KzJwG59Yt9mYNT4Bg
zkrv2gcd9hcm4gkppnsbbgqsd7mth7jd
atlassian-sending-domain-verification=f2f45e42-2786-47a6-b7b6-2c94d71e68b6
google-site-verification=23PyQ8_HElUn5qTj4whEJ03YGOKdpQSgYupfp_Gdbs0
google-site-verification=1I8r75Kusl-vSj2NIgt6fBxwgTUW25oeHWy7RDfpb9w
apple-domain-verification=LBVWj6scopEmbpxI
tiktok-developers-site-verification=bpEtMFa6RrUEVsCPuRr7N8eq7ryWzLmt
MS=EEF77373FCFD46EBDD78FF805087F267506F538E
factorial-domain-verification=xyBjcWXR4RWpbZiBm4XpJX7f1Hqmhy837v3dtKVB7NKH6v6dHo...
SFMC-7HypAaThfLvwozSEwEL9j5C-OgqpxCp4tCEUhLmx
7vtbdbv0fpknn9vtsqxm823rms20r854
anthropic-domain-verification-jdd88z=9knmd39iD2EGOz6B345PXjUpn
2709c661f0811686ab7d07bf0018e325
openai-domain-verification=dv-I4UGsopdzMinK6kxtXtBNg2g
google-site-verification=Q38jh-Pc6qGbJTqYs9aw2tysRz-OfWuyAAYVe9NFKP4
anthropic-domain-verification-82qr13=0xyagvX5MhBdZHanZB64sXz1T
notion-domain-verification=lzvmW06jBDVPwJccvHQ4CPRMZ8QG7yiwuyjFM4bC2RY
MS=ms34125468
cursor-domain-verification-r1hfc8=OI2V2pqMofMENc5dRLGbuSSJl
google-site-verification=j2LuXa3kOWLfD5MPx50CRI6wSzBC_csHYlrixZRETKs
atlassian-domain-verification=1vZOjoX6JGZoV3dIe8v8LOTrGfUcI9MBapMIhmQLcALCl251vK...
postman-domain-verification=7b9f1332acec33e83b552b43856f9182a362408f0c406450149b...
SPF v=spf1 include:_spf.salesforce.com include:spf.mandrillapp.com include:amazonses...
anthropic-domain-verification-pe7r86=FDpDOZkfaaOdeWKTuqLLaFYgL
CAALookup not available with standard resolver
Resolved in 84 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), 179 ms total
PASS
1 redirect(s), 179 ms total
Info::
Single redirect
Got: https://freepik.com → https://www.freepik.com/ (301)
Info::
WWW normalization redirect

https://freepik.com

63 ms · HTTP/1.1

301

https://www.freepik.com/

115 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://freepik.com30163 msHTTP/1.1
2https://www.freepik.com/403115 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.freepik.com/
200https://freepik.com/

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
freepik.com — via IONOS SE, 15 years, 11 months old, hosted on Google Cloud
PASS
freepik.com — via IONOS SE, 15 years, 11 months old, hosted on Google Cloud
Info::
Domain registered until Aug 4, 2026 (3 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: IONOS SE
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

21 days

August 4, 2026

SSL certificate

50 days

Issued by Google Trust Services

Domain age

15 years, 11 months

Registered August 4, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.160.205.140

Registrar

IONOS SE

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 DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar IONOS SE
Created August 4, 2010 (15 years, 11 months ago)
Expires August 4, 2026 (3 months)
Last Updated August 5, 2025
Name Servers ns10.dnsmadeeasy.com, ns11.dnsmadeeasy.com, ns12.dnsmadeeasy.com, ns13.dnsmadeeasy.com
DNSSEC Not enabled
Hosting
IP Address 34.160.205.140
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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 96 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
35 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
26 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
96 ms
Total Time Total request time from DNS lookup through full response.
96 ms

Connection waterfall

DNS Lookup 35 ms TCP Connect 17 ms TLS Handshake 26 ms Server Processing 18 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback