Skip to content
https://vungle.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 2 REVIEW 1 FIX
D
Redirect Chain
Action
2 redirect(s), 1007 ms total
FIX
2 redirect(s), 1007 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://liftoff.io/
Warning::
Redirect overhead: 1007 ms total
Got: 1007 ms
Info::
Cross-domain redirect detected

https://vungle.com

474 ms · HTTP/1.1

301

https://liftoff.io/

273 ms · HTTP/1.1

302

https://liftoff.ai/

261 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://vungle.com301474 msHTTP/1.1cloudflare
2https://liftoff.io/302273 msHTTP/1.1cloudflare
3https://liftoff.ai/200261 msHTTP/1.1cloudflare

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

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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
44 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

44
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
2 A records, 73 ms lookup
PASS
2 A records, 73 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 141.193.213.10, 141.193.213.11
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: a9-66.akam.net, a2-66.akam.net, a1-5.akam.net, a7-65.akam.net, a4-64.akam.net, a28-67.akam.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
Info::
DNS resolution time: 73 ms
Got: 73 ms
A141.193.213.10, 141.193.213.11
AAAA
CNAME
NSa9-66.akam.net, a2-66.akam.net, a1-5.akam.net, a7-65.akam.net, a4-64.akam.net, a28-67.akam.net
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
google-site-verification=0zRm52rcWn-yII3AK0gxMoSpN8KwcfOjRi_Hq8akbpk
google-site-verification=sYZNRqJS3maOx3tBcs6HAAhFB49Mpo6uatuNr5FqaVc
lucid-verification=x55UjUfZ#7Dn
pardot710783=e5df74ec1cb011f8f1bd87f0e55c3b7c5487ff2780ee9abe1c85686ffec70486
cloudhealth=e11c50f8-ba0e-4873-bd83-3ab6eb2d7fc7
google-site-verification=ujg4H5z88syLz8zRc_Q9GOTEwKGSP_J1K1DlTIkHln0
MS=ms67965465
apple-domain-verification=yUS3ZsFr46UbTEx3
docusign=1c19d2d9-1069-4173-a92d-5d9d9b80d5e7
0ed1fe018a14dce4fa58304350acec7e1301c8548e
google-site-verification=8Kt5Q3JGeAwJwnmeAt3B3oO90jWSUDjxUjF3rlMwPwk
OSSRH-65218
SPF v=spf1 include:_spf.google.com include:sendgrid.net include:6410061.spf02.hubspo...
google-site-verification=clx1pp0yithbUHF2WN5Vf379Jf4E6j5gWub9SPjckyU
tinfoil-site-verification: 01a77ab510528e2228f79f14aba7c25f556367d8=3f15dcb0c15c...
google-site-verification=Tc27U5-nZW0fPETGJC8AISvxfzzkKMJYuBbf_-K7kYM
google-site-verification=tQa94BHuOYEtej7-uHwp-aHh3MC_0li5xsA9wYXs08g
adobe-idp-site-verification=d81785899a6d24611bfb0155d2da657859fb3506691ba56b1e13...
atlassian-domain-verification=1VdEeHNGYUuI7dkmPWZ8duP9LTl+AIdHC7ee7Fx4cPKt34uKnG...
CAALookup not available with standard resolver
Resolved in 73 ms

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, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 82 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
Sitemap index with 6 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 82 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Crawl-delay: 10
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)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

301http://vungle.com/ https://vungle.com/

Consistent

A+
Domain Intelligence
vungle.com — via Moniker Online Services LLC, 15 years, 8 months old, hosted on Cloudflare
PASS
vungle.com — via Moniker Online Services LLC, 15 years, 8 months old, hosted on Cloudflare
Info::
Domain registered until Oct 26, 2026 (6 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: Moniker Online Services LLC
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: Cloudflare
Got: AS209242
Domain expiry

133 days

October 26, 2026

SSL certificate

44 days

Issued by Let's Encrypt

Domain age

15 years, 8 months

Registered October 26, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS209242

141.193.213.10

Registrar

Moniker Online Services LLC

Unlocked 6 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 Moniker Online Services LLC
Created October 26, 2010 (15 years, 8 months ago)
Expires October 26, 2026 (6 months)
Last Updated November 25, 2025
Name Servers a1-5.akam.net, a2-66.akam.net, a28-67.akam.net, a4-64.akam.net, a7-65.akam.net, a9-66.akam.net
DNSSEC Not enabled
Hosting
IP Address 141.193.213.10
ASN AS209242 (CLOUDFLARESPECTRUM Cloudflare, Inc., US)
Provider Cloudflare
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 542 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.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
9 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
543 ms
Total Time Total request time from DNS lookup through full response.
543 ms

Connection waterfall

DNS Lookup 35 ms TCP Connect 1 ms TLS Handshake 9 ms Server Processing 497 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: MAD)
Got: cf-ray: 9ed4ce241b6acfad-MAD
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9ed4ce241b6acfad-MAD
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback