Skip to content
https://9gag.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
7 PASS 2 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
TLS Certificate Expiry & Recommendations
78 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
5 A records, 46 ms lookup
PASS
5 A records, 46 ms lookup
Info::
Resolves to 5 IPv4 address(es)
Got: 104.16.103.144, 104.16.105.144, 104.16.107.144, 104.16.104.144, 104.16.106.144
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-408.awsdns-51.com, ns-629.awsdns-14.net, ns-1673.awsdns-17.co.uk, ns-1294.awsdns-33.org
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: 46 ms
Got: 46 ms
A104.16.103.144, 104.16.105.144, 104.16.107.144, 104.16.104.144, 104.16.106.144
AAAA
CNAME
NSns-408.awsdns-51.com, ns-629.awsdns-14.net, ns-1673.awsdns-17.co.uk, ns-1294.awsdns-33.org
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 aspmx4.googlemail.com
30 aspmx5.googlemail.com
30 aspmx3.googlemail.com
TXT
facebook-domain-verification=sewwuscekyx7lzpw1sqpw99js0yk9g
globalsign-domain-verification=FnXWfFjPqReOGiIH8ITAbUasqKxnix6ftvTUzPOKHF
google-site-verification=gnbwBUuZfO2BFehBSGAUwK129i8j1vBQQ9bNbaDooLk
dvqcym11fc0d.cloudfront.net
google-site-verification=g4d9QwibWGtigYptjjl54uZm2idXPVeIfmxDJADPx9w
SPF v=spf1 include:_spf.google.com include:sendgrid.net include:shops.shopify.com in...
apple-domain-verification=Gm2hvxbVPimp6HI8
CAALookup not available with standard resolver
Resolved in 46 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://9gag.com

https://9gag.com

92 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://9gag.com20092 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 319 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
Sitemap index with 4 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 319 B Sitemaps referenced 0 User-agents Mediapartners-Google, * Blocking No — crawling allowed
# Robots.txt file for https://9gag.com
# All robots will spider the domain

User-agent: Mediapartners-Google
Allow: /

User-agent: *
Disallow: /gag-in-app/*
Disallow: /aid/*
Disallow: /settings*
Disallow: /notifications*
Disallow: /connect/*
Disallow: /others/*
Disallow: /static/*
Disallow: /static/ads/*
Disallow: /?

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.9gag.com/
200https://9gag.com/

HTTP → HTTPS

301http://9gag.com/ https://9gag.com/

Consistent

A+
Domain Intelligence
9gag.com — via Name.com, Inc., 18 years, 3 months old, hosted on Cloudflare
PASS
9gag.com — via Name.com, Inc., 18 years, 3 months old, hosted on Cloudflare
Info::
Domain registered until Apr 12, 2027 (11 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: Name.com, 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: Cloudflare
Got: AS13335
Domain expiry

271 days

April 12, 2027

SSL certificate

78 days

Issued by Google Trust Services

Domain age

18 years, 3 months

Registered April 12, 2008

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.16.103.144

Registrar

Name.com, 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 Name.com, Inc.
Created April 12, 2008 (18 years, 3 months ago)
Expires April 12, 2027 (11 months)
Last Updated April 7, 2026
Name Servers ns-1294.awsdns-33.org, ns-1673.awsdns-17.co.uk, ns-408.awsdns-51.com, ns-629.awsdns-14.net
DNSSEC Not enabled
Hosting
IP Address 104.16.103.144
ASN AS13335 (CLOUDFLARENET - 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 132 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
45 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
130 ms
Total Time Total request time from DNS lookup through full response.
132 ms

Connection waterfall

DNS Lookup 45 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 46 ms Content Transfer 3 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f07d577dd8f6fa6-CDG
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: 9f07d577dd8f6fa6-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback