Skip to content
https://viber.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
4 PASS 3 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 1034 ms total
FIX
2 redirect(s), 1034 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
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.viber.com:443/
Warning::
Redirect overhead: 1034 ms total
Got: 1034 ms

https://viber.com

749 ms · HTTP/1.1

301

https://www.viber.com:443/

282 ms · HTTP/1.1

302

https://www.viber.com/en/

3 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://viber.com301749 msHTTP/1.1awselb/2.0
2https://www.viber.com:443/302282 msHTTP/1.1nginx
3https://www.viber.com/en/2003 msHTTP/1.1nginx

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

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
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 181 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 181 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp/wp-admin/
Disallow: /en/terms/viber-dating-terms-and-conditions
Disallow: /en/terms/viber-dating-community-guidelines
Allow: /wp/wp-admin/admin-ajax.php
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
HTTP Probe Timing
Total 882 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
104 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
259 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
261 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
882 ms
Total Time Total request time from DNS lookup through full response.
882 ms

Connection waterfall

DNS Lookup 104 ms TCP Connect 259 ms TLS Handshake 261 ms Server Processing 259 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
142 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

142
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, 645 ms lookup
PASS
2 A records, 645 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 54.163.26.51, 52.205.155.161
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:1f18:2092:1a04:6f80:9ec6:f688:2a6, 2600:1f18:2092:1a05:173e:9941:9c66:cca7
Info::
4 nameserver(s) configured
Got: ns-1529.awsdns-63.org, ns-1545.awsdns-01.co.uk, ns-167.awsdns-20.com, ns-912.awsdns-50.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 (645 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 645 ms
A54.163.26.51, 52.205.155.161
AAAA2600:1f18:2092:1a04:6f80:9ec6:f688:2a6, 2600:1f18:2092:1a05:173e:9941:9c66:cca7
CNAME—
NSns-1529.awsdns-63.org, ns-1545.awsdns-01.co.uk, ns-167.awsdns-20.com, ns-912.awsdns-50.net
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 alt2.aspmx.l.google.com
40 aspmx2.googlemail.com
50 aspmx3.googlemail.com
TXT
MS=1E688336536DB4611A9787DA98C0D14029854FBF
MS=ms23211621
ZOOM_verify_T_2MYm3FSaKSu4P6DlKXnA
anthropic-domain-verification-a85jj0=gCCIwjwywMdQkEdSaIwdezkGO
apple-domain-verification=bgpv4gORhyGA7KGj
atlassian-domain-verification=1APVEY6SlEQdjkuyX522H4Hv8n9JVpjySwOdrDRBsC/jOcVxcY...
atlassian-sending-domain-verification=241a5ca5-0489-4e49-bf9a-826046566598
browserstack-domain-verification=80db929c-75a6-4f1d-a647-19ddca5bf981
ciscocidomainverification=64ea3b9e1916be67c0efc2ef218b4feadde89fe765460c37798662...
cursor-domain-verification-j6pa4r=0HyAdXLDdx4HZG2wGH7LiqVcf
figma-domain-verification=8e66a23da8fd71f0b69c13b8a3f26ceec13ae728f7c273f6bd3751...
globalsign-domain-verification=pmkDankb_54bT6YZ6nh8dh2bmLCAHwpwYJogWviA1o
google-site-verification=G4yZWnJS0EsYw8wdWj1FX-CJoaGVR5aUsRgtqhi23sw
google-site-verification=Ja-gcdAlYdHJn4jQ92tLQe6Ms1u1klnt56nPpzO9OHo
google-site-verification=JkKJ3lZl0wD3DOjaTf98CnaJVY9z6U3EO5TAGQFHObk
google-site-verification=Jr_kkRWwpSO_KozChN1p-JYATIUbmXaVv8NFoXI50Os
google-site-verification=Q6qVQ4I6FUDrnw3XqJqL95trWi43PQYNNsBS5uBBEj4
google-site-verification=uM9nFp2TFd0FAq4kehUsi_0Evwl_K9H_3vPa-AxkO70
jamf-site-verification=7QDu3f2j8SuxOC74U5XCKg
lovable_verification=7WBXfPGo9s46AXhF1XmF
mixpanel-domain-verify=3c16ee6e-9630-4fa4-89c7-a58f2f5a1fc1
SPF v=spf1 ip4:194.90.232.83 ip4:18.159.165.123 ip4:194.90.232.0/24 include:amazonse...
wiz-domain-verification=ce52a6c1b3a67a7960abf557e5017904dcf871598e52b216fb76674c...
CAALookup not available with standard resolver
Resolved in 645 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.

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+
IPv6 Readiness
IPv6 reachable (253 ms)
PASS
IPv6 reachable (253 ms)
Info::
IPv6 is configured and reachable at 2600:1f18:2092:1a04:6f80:9ec6:f688:2a6, 2600:1f18:2092:1a05:173e:9941:9c66:cca7
Got: 253 ms connect
IPv6 Ready
AAAA Records 2600:1f18:2092:1a04:6f80:9ec6:f688:2a6, 2600:1f18:2092:1a05:173e:9941:9c66:cca7 Connection Reachable (253 ms)
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

302https://www.viber.com/
200https://viber.com/

Preferred variant: non-www

HTTP → HTTPS

301http://viber.com/ → https://www.viber.com:443/

Consistent

A+
Domain Intelligence
viber.com — via GoDaddy.com, LLC, 26 years, 11 months old
PASS
viber.com — via GoDaddy.com, LLC, 26 years, 11 months old
Info::
Domain registered until Sep 7, 2028 (2 years, 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: GoDaddy.com, 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.
Domain expiry

786 days

September 7, 2028

SSL certificate

142 days

Issued by Amazon

Domain age

26 years, 11 months

Registered September 7, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:1f18:2092:1a05:173e:9941:9c66:cca7

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC
Created September 7, 1999 (26 years, 11 months ago)
Expires September 7, 2028 (2 years, 5 months)
Last Updated April 28, 2025
Name Servers ns-1529.awsdns-63.org, ns-1545.awsdns-01.co.uk, ns-167.awsdns-20.com, ns-912.awsdns-50.net
DNSSEC Not enabled
Hosting
IP Address 2600:1f18:2092:1a05:173e:9941:9c66:cca7
Data source: rdap (0.1s)

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

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

Send Feedback