Skip to content
https://adjust.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 Sao Paulo, Brazil
307 Temporary Redirect
Checks
9
5 PASS 4 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
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
182 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

182
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: gru1::lkwr7-1776362991969-326013f4437e
CDN Detected: Vercel
Provider Vercel Evidence x-vercel-id: gru1::lkwr7-1776362991969-326013f4437e
A
DNS Records
1 A records, 356 ms lookup
PASS
1 A records, 356 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::
8 nameserver(s) configured
Got: ns04.adjust.works, ns03.adjust.works, dns2.p09.nsone.net, dns4.p09.nsone.net, ns02.adjust.works, ns01.adjust.works, dns3.p09.nsone.net, dns1.p09.nsone.net
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
Warning::
DNS resolution is slow (356 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 356 ms
A76.76.21.21
AAAA
CNAME
NSns04.adjust.works, ns03.adjust.works, dns2.p09.nsone.net, dns4.p09.nsone.net, ns02.adjust.works, ns01.adjust.works, dns3.p09.nsone.net, dns1.p09.nsone.net
MX
10 aspmx.l.google.com
20 alt2.aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 aspmx3.googlemail.com
30 aspmx2.googlemail.com
TXT
SPF v=spf1 mx ip4:136.243.153.110/26 ip4:136.243.38.205/26 ip4:138.201.130.67/26 ip4...
fastly-domain-delegation-NaZ93uPO3CPGk4KzuyEO-465938-02-16-22
zdm1585nx3jp4j6rgmc0ftm44lyffrcc
MS=ms91392298
839FC53FDA
4E59304358
_2mgx0gdbme3ki5s337rt8jug47oa8i8
miro-verification=466ab057897152b6f77a03a39837da20e9dcd016
openai-domain-verification=dv-WsOr3PtgzRhQ28QaIILomJim
atlassian-domain-verification=raDxE7jPrFu+9q16RNhQMpc1N2cII9sRSSpxGo6Rur0Fvq3gAb...
h1-domain-verification=N3L6LWD32uB8YuRHHkJKHhTnzigvw2fe5V4F9xCWoM3hTUmG
figma-domain-verification=1149781de96e4b177fb8e460ea26e6f36e8f08497eba0a7ac30f53...
projectdiscovery-verification=71eb0b3563
anthropic-domain-verification-mz70bc=Nk7vXemxtlnom9lztnSGEsmRd
_u6sjnkq3kiw6ec2hylz78kflt54w753
CAALookup not available with standard resolver
Resolved in 356 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A
Redirect Chain
1 redirect(s), 160 ms total
PASS
1 redirect(s), 160 ms total
Info::
Single redirect
Got: https://adjust.com → https://www.adjust.com/ (307)
Info::
WWW normalization redirect

https://adjust.com

134 ms · HTTP/1.1

307

https://www.adjust.com/

26 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://adjust.com307134 msHTTP/1.1Vercel
2https://www.adjust.com/42926 msHTTP/1.1Vercel

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

www / non-www

429https://www.adjust.com/
200https://adjust.com/

HTTP → HTTPS

308http://adjust.com/ https://adjust.com/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
adjust.com — via Mesh Digital Limited, 30 years, 11 months old, hosted on AWS
PASS
adjust.com — via Mesh Digital Limited, 30 years, 11 months old, hosted on AWS
Info::
Domain registered until Sep 26, 2026 (5 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: Mesh Digital Limited
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

104 days

September 26, 2026

SSL certificate

182 days

Issued by DigiCert Inc

Domain age

30 years, 11 months

Registered September 27, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

76.76.21.21

Registrar

Mesh Digital Limited

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 Mesh Digital Limited
Created September 27, 1995 (30 years, 11 months ago)
Expires September 26, 2026 (5 months)
Last Updated September 25, 2025
Name Servers dns1.p09.nsone.net, dns2.p09.nsone.net, ns01.adjust.works, ns02.adjust.works
DNSSEC Not enabled
Hosting
IP Address 76.76.21.21
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (3.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 16 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
4 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.
17 ms
Total Time Total request time from DNS lookup through full response.
17 ms

Connection waterfall

DNS Lookup 4 ms TCP Connect 1 ms TLS Handshake 8 ms Server Processing 3 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