Skip to content
https://coub.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
302 Found
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
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 273 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 references 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

robots.txt 200 OK
Size 273 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Disallow: /embed
Disallow: /sources
Disallow: /account/edit
Disallow: /create
Disallow: /chat
Disallow: /oauth
Disallow: /auth
Disallow: /feed
Disallow: /search
Disallow: /set_new_password/*
Disallow: */remix
Sitemap: https://coub.com/sitemaps/sitemap.xml.gz

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
42 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
A+
DNS Records
1 A records, 4 ms lookup
PASS
1 A records, 4 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 95.213.253.92
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-1316.awsdns-36.org, ns-1712.awsdns-22.co.uk, ns-189.awsdns-23.com, ns-762.awsdns-31.net
Info::
7 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: 4 ms
Got: 4 ms
A95.213.253.92
AAAA
CNAME
NSns-1316.awsdns-36.org, ns-1712.awsdns-22.co.uk, ns-189.awsdns-23.com, ns-762.awsdns-31.net
MX
1 aspmx.l.google.com
3 alt1.aspmx.l.google.com
3 alt2.aspmx.l.google.com
5 aspmx4.googlemail.com
5 aspmx2.googlemail.com
5 aspmx3.googlemail.com
5 aspmx5.googlemail.com
TXT
atlassian-domain-verification=pkahmM3xIbEa00faxSScpw218b29Z7oeUMiOn17sH2v3yOuqVj...
google-site-verification=YILgkunzazXHlPUY0uMB-PU6KWM9aosmZaekf3x4yMg
qn2k82bd33ldv5n82mtjd50t0h7d8mqh
SPF v=spf1 ip4:212.41.12.227 include:_spf.google.com include:email.freshdesk.com ~a...
yandex-verification: 5de7f567bbd7ec28
CAALookup not available with standard resolver
Resolved in 4 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), 444 ms total
PASS
1 redirect(s), 444 ms total
Info::
Single redirect
Got: https://coub.com → https://coub.com/featured/creators (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://coub.com

https://coub.com

176 ms · HTTP/1.1

302

https://coub.com/featured/creators

268 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://coub.com302176 msHTTP/1.1nginx
2https://coub.com/featured/creators200268 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

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

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.coub.com/
200https://coub.com/

Preferred variant: non-www

HTTP → HTTPS

301http://coub.com/ https://coub.com/

Consistent

A+
Domain Intelligence
coub.com — via GoDaddy.com, LLC, 23 years, 10 months old, hosted on SELECTEL, RU
PASS
coub.com — via GoDaddy.com, LLC, 23 years, 10 months old, hosted on SELECTEL, RU
Info::
Domain registered until Oct 19, 2029 (3 years, 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: 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.
Info::
Hosting: SELECTEL, RU
Got: AS49505
Domain expiry

1222 days

October 19, 2029

SSL certificate

42 days

Issued by Let's Encrypt

Domain age

23 years, 10 months

Registered October 19, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

SELECTEL, RU

ASN AS49505

95.213.253.92

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 October 19, 2002 (23 years, 10 months ago)
Expires October 19, 2029 (3 years, 6 months)
Last Updated January 29, 2024
Name Servers ns-1316.awsdns-36.org, ns-1712.awsdns-22.co.uk, ns-189.awsdns-23.com, ns-762.awsdns-31.net
DNSSEC Not enabled
Hosting
IP Address 95.213.253.92
ASN AS49505 (SELECTEL, RU)
Provider SELECTEL, RU
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 174 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.
39 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
83 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
175 ms
Total Time Total request time from DNS lookup through full response.
175 ms

Connection waterfall

DNS Lookup 4 ms TCP Connect 39 ms TLS Handshake 83 ms Server Processing 50 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