Skip to content
https://meltwater.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
307 Temporary Redirect
Checks
9
5 PASS 4 REVIEW
B
Redirect Chain
2 redirect(s), 339 ms total
REVIEW
2 redirect(s), 339 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect

https://meltwater.com

65 ms · HTTP/1.1

307

https://www.meltwater.com/

159 ms · HTTP/1.1

301

https://www.meltwater.com/en

115 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://meltwater.com30765 msHTTP/1.1Vercel
2https://www.meltwater.com/301159 msHTTP/1.1Vercel
3https://www.meltwater.com/en200115 msHTTP/1.1Vercel

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
Vercel
REVIEW
Vercel
Info::
Site is served via Vercel CDN
Got: x-vercel-id: cdg1::x846g-1776816299102-a5be4e790109
CDN Detected: Vercel
Provider Vercel Evidence x-vercel-id: cdg1::x846g-1776816299102-a5be4e790109
A+
DNS Records
1 A records, 84 ms lookup
PASS
1 A records, 84 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 76.76.21.21
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-1790.awsdns-31.co.uk, ns-393.awsdns-49.com, ns-1510.awsdns-60.org, ns-982.awsdns-58.net
Info::
2 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
A76.76.21.21
AAAA
CNAME
NSns-1790.awsdns-31.co.uk, ns-393.awsdns-49.com, ns-1510.awsdns-60.org, ns-982.awsdns-58.net
MX
0 de-smtp-inbound-1.mimecast.com
5 de-smtp-inbound-2.mimecast.com
TXT
1password-site-verification=TKKICWJ3SNCHTOCI6HFMF54QB4
eFxS5qJ3fOej8L8KMm9xxUZiynRk4VLpoXD9ALvkIu0=
beautifulai-site-verification=6384054f-dc23-4f48-b078-48ac01d2e7cd
OvUOFtpZyHrzig3hbLJWKcvfw+EdD480gx9B618CvvA=
google-site-verification=nkmXfGaJAokkpGP5XqvxPum7Q0Lng2QGf1KVNL_oIR0
google-site-verification=CZZndzWaG4-c0WLSs5RXD9yxmbVNalrg0k5p9_qzY2M
gxj4rskgygzlz62lc9hf74q1k5d92ltv
5fa2b4a893514f5093664204bd115931
amazonses:cCr/QoTzmcTEZYvMtqbv0xr/q5YAlw2KEdftck41e84=
google-site-verification=mEZsnEjEsnerIeX8iu6_v-rsDOKKhhQO25i_tu-26xc
openai-domain-verification=dv-IWdLZQu76sQl51Z5z412bfnl
google-site-verification=tRgFVYv4rHHa3_IpYMLSW3POXEN-hsXGXtKM3ZDeXlA
zapier-domain-verification-challenge=2e3d3be0-8e3c-4949-8682-d0266019b030
SPF v=spf1 include:de._netblocks.mimecast.com include:_spf.meltwater.com include:_sp...
jamf-site-verification=FlLKGmeueW94YgdKUBIPcg
asv=e65cb34e6ee9fd7894e6282d09973839
anthropic-domain-verification-ncjp58=HFi6fB3WPZ3bg1gqplWgSiLKg
atlassian-domain-verification=bZK0gPVqrI7EiU8m8eS4i0Ks1Y8flvHU4WCuFtNpQbhyyjmelv...
zapier-domain-verification-challenge=a86c5e7c-3830-49c8-9bb2-3ff4acacbfff
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
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 90 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references sitemap

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 200 OK
Size 90 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /*?uid=*

Sitemap: https://www.meltwater.com/sitemap.xml

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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: non-www)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

301https://www.meltwater.com/
200https://meltwater.com/

Preferred variant: non-www

HTTP → HTTPS

308http://meltwater.com/ https://meltwater.com/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
meltwater.com — via Amazon Registrar, Inc., 26 years, 6 months old, hosted on AWS
PASS
meltwater.com — via Amazon Registrar, Inc., 26 years, 6 months old, hosted on AWS
Info::
Domain registered until Feb 22, 2027 (10 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: Amazon Registrar, 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: AWS
Got: AS16509
Domain expiry

254 days

February 22, 2027

SSL certificate

33 days

Issued by Let's Encrypt

Domain age

26 years, 6 months

Registered February 22, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

76.76.21.21

Registrar

Amazon Registrar, Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Amazon Registrar, Inc.
Created February 22, 2000 (26 years, 6 months ago)
Expires February 22, 2027 (10 months)
Last Updated January 18, 2026
Name Servers ns-1510.awsdns-60.org, ns-1790.awsdns-31.co.uk, ns-393.awsdns-49.com, ns-982.awsdns-58.net
DNSSEC Not enabled
Hosting
IP Address 76.76.21.21
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 28 ms TCP Connect 1 ms TLS Handshake 48 ms Server Processing 29 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