Skip to content
https://boredpanda.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
4
PASS
4
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
4 PASS 4 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.

B
Redirect Chain
2 redirect(s), 834 ms total
REVIEW
2 redirect(s), 834 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
2-hop chain could be reduced to 1 hop
Redirect directly from https://boredpanda.com to https://www.boredpanda.com/
Info::
Redirect overhead: 834 ms total
Got: 834 ms

https://boredpanda.com

378 ms · HTTP/1.1

301

http://www.boredpanda.com/

13 ms · HTTP/1.1

301

https://www.boredpanda.com/

442 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://boredpanda.com301378 msHTTP/1.1nginx
2http://www.boredpanda.com/30113 msHTTP/1.1CloudFront
3https://www.boredpanda.com/200442 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

Redirect directly from https://boredpanda.com to https://www.boredpanda.com/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.boredpanda.com/
200https://boredpanda.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B
TLS Certificate Expiry & Recommendations
312 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

312
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
  • 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
4 A records, 5 ms lookup
PASS
4 A records, 5 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 34.201.211.182, 98.85.160.255, 34.203.1.89, 3.89.175.144
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1425.awsdns-50.org, ns-173.awsdns-21.com, ns-1985.awsdns-56.co.uk, ns-972.awsdns-57.net
Info::
1 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: 5 ms
Got: 5 ms
A34.201.211.182, 98.85.160.255, 34.203.1.89, 3.89.175.144
AAAA—
CNAME—
NSns-1425.awsdns-50.org, ns-173.awsdns-21.com, ns-1985.awsdns-56.co.uk, ns-972.awsdns-57.net
MX
10 aspmx.l.google.com
TXT
MS=E04C457D679181C1054598D9F097241502D2B900
MS=ms42183495
apple-domain-verification=hops-EdsP_znUZ0tgSnyMFqx9WcQ6J6CLUlLwNJuseY
brevo-code:59ddf176bd2029a7dea7a297ba5967ef
facebook-domain-verification=fgwdxllanmj6qtcuvmke1si9ec60ia
google-site-verification=7IVwsmZnsAkCK_7cAFwmFfKsOt-dEkibijx09hJfQhM
google-site-verification=E-VWzamHJVxn2aKoEbD2dNX18GG_rEuHAJIAcsZ9JQY
google-site-verification=KIIUiAJna3_1-eDilP2A9ENUy2oiWftdyHXyCMhnz3s
google-site-verification=MxIMpuiT8s52Vltu5GksnMWb3AmEfjHaawL4ii8SD_Q
google-site-verification=QyUw3s4mkxY3wZMMy4oMT3yHhdCqtiBuusYhmvAdgVM
google-site-verification=XuF5a9eahvWOgNLrh7WkeiFQpnIjdbpEgbWPZ0a1oYY
trustpilot-one-time-verification-id=9eb08d90-b03e-4784-821f-4256acbae37d
SPF v=spf1 a mx include:_spf.mlsend.com include:_spf.google.com include:spf.mailjet....
CAALookup not available with standard resolver
Resolved in 5 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 10 URLs
PASS
robots.txt present, sitemap with 10 URLs
Info::
robots.txt is present
Got: 1267 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 10 entries
Info::
Sitemap index with 10 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1267 B Sitemaps referenced 6 User-agents *, facebookexternalhit, Bytespider, Baiduspider, PetalBot, TikTokSpider, Twitterbot, Bingbot Blocking No — crawling allowed
User-agent: facebookexternalhit
Allow: /

User-agent: Bytespider
Disallow: /

User-agent: Baiduspider
Disallow: /

User-agent: PetalBot
Disallow: /

User-agent: TikTokSpider
Disallow: /

User-agent: Twitterbot
Allow: /*?utm_

User-agent: Bingbot
Disallow: /?s=
Disallow: /search/

User-agent: *
Allow: /
Disallow: /*wp-admin/
Disallow: /*wp-includes
Disallow: /*wp-content
Disallow: /*wp-json
Disallow: /contributor/

Allow: /*?cexp_id
Allow: /*?show=trending
Allow: /*?show=recent
Allow: /*wp-includes*.jpg
Allow: /*wp-content*.jpg
Allow: /*wp-includes*.jpeg
Allow: /*wp-content*.jpeg
Allow: /*wp-includes*.jpe
Allow: /*wp-content*.jpe
Allow: /*wp-includes*.png
Allow: /*wp-content*.png
Allow: /*wp-includes*.css
Allow: /*wp-content*.css
Allow: /*wp-includes*.js
Allow: /*wp-content*.js
Allow: /*wp-includes*.gif
Allow: /*wp-content*.gif
Allow: /*wp-includes*.svg
Allow: /*wp-content*.svg
Allow: /*wp-includes*.webp
Allow: /*wp-content*.webp


Sitemap: https://www.boredpanda.com/sitemap.xml
Sitemap: https://www.boredpanda.com/tags-sitemap.xml
Sitemap: https://www.boredpanda.com/categories-sitemap.xml
Sitemap: https://www.boredpanda.com/news-sitemap.xml
Sitemap: https://www.boredpanda.com/authors-sitemap.xml
Sitemap: https://www.boredpanda.com/games-sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 10 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
boredpanda.com — via GoDaddy.com, LLC, 16 years, 11 months old, hosted on AWS
PASS
boredpanda.com — via GoDaddy.com, LLC, 16 years, 11 months old, hosted on AWS
Info::
Domain registered until Jul 23, 2029 (3 years, 3 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: AWS
Got: AS14618
Domain expiry

1136 days

July 23, 2029

SSL certificate

312 days

Issued by Amazon

Domain age

16 years, 11 months

Registered July 23, 2009

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

34.203.1.89

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 July 23, 2009 (16 years, 11 months ago)
Expires July 23, 2029 (3 years, 3 months)
Last Updated October 1, 2022
Name Servers ns-1425.awsdns-50.org, ns-173.awsdns-21.com, ns-1985.awsdns-56.co.uk, ns-972.awsdns-57.net
DNSSEC Not enabled
Hosting
IP Address 34.203.1.89
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

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 381 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
6 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
93 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
188 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
381 ms
Total Time Total request time from DNS lookup through full response.
381 ms

Connection waterfall

DNS Lookup 6 ms TCP Connect 93 ms TLS Handshake 188 ms Server Processing 94 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