Infrastructure - https://Funnytimes.com BeaverCheck Audit

B

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

DNSSEC is not deployed

The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

B

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

No CAA records published

Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

C

Reverse DNS

Action

0/4 IPs match cert SAN

REVIEW

0/4 IPs match cert SAN

PTR lookup failed for 162.159.135.42: lookup 162.159.135.42: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 162.159.134.42: lookup 162.159.134.42: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 2606:4700:7::a29f:872a: lookup 2606:4700:7::a29f:872a: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 2606:4700:7::a29f:862a: lookup 2606:4700:7::a29f:862a: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

B

HTTP Probe Timing

Total 883 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

12 ms

TCP Connect

1 ms

TLS Handshake

9 ms

Time to First Byte

602 ms

Total Time

884 ms

Connection waterfall

DNS Lookup 12 ms TCP Connect 1 ms TLS Handshake 9 ms Server Processing 580 ms Content Transfer 282 ms

B

TLS Certificate Expiry & Recommendations

87 days until leaf cert expires — 2 issues to address

REVIEW

Certificate validity

87

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

B

Operational Status Page

No status page link detected

REVIEW

No status page link detected

No operational status page link detected

Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

B

Health Check Endpoint

No conventional health endpoint found

REVIEW

No conventional health endpoint found

Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.

A+

DNS Records

2 A records, 12 ms lookup

PASS

2 A records, 12 ms lookup

Resolves to 2 IPv4 address(es)

Got: 162.159.135.42, 162.159.134.42

Has 2 IPv6 (AAAA) record(s)

Got: 2606:4700:7::a29f:872a, 2606:4700:7::a29f:862a

2 nameserver(s) configured

Got: daisy.ns.cloudflare.com, mustafa.ns.cloudflare.com

5 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 12 ms

Got: 12 ms

A	162.159.135.42, 162.159.134.42
AAAA	2606:4700:7::a29f:872a, 2606:4700:7::a29f:862a
CNAME	—
NS	daisy.ns.cloudflare.com, mustafa.ns.cloudflare.com
MX	1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com
TXT	GOOGLE-SITE-VERIFICATION=UQ_6G_WNKJAP0TAM1L-XWNJ8PJGRDKUDPCTK8SNASY0 google-site-verification=OVn_hEVY3KSD_PICBDbeZT93WyGzcgdDWZ-98sKdB80 SPF v=spf1 +mx +a +ip4:76.12.128.233 +ip4:204.12.102.47 +include:spf.safesecureweb.c...
CAA	Lookup not available with standard resolver

Resolved in 12 ms

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Multi-Resolver DNS Speed

Mean 6ms across 3 resolvers (spread 10ms)

PASS

Mean 6ms across 3 resolvers (spread 10ms)

Cloudflare: 1ms

Got: 1ms via 1.1.1.1:53

Quad9: 8ms

Got: 8ms via 9.9.9.9:53

Google: 11ms

Got: 11ms via 8.8.8.8:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://Funnytimes.com

https://Funnytimes.com

49 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://Funnytimes.com	200	49 ms	HTTP/1.1	cloudflare

A+

IPv6 Readiness

IPv6 reachable (1 ms)

PASS

IPv6 reachable (1 ms)

IPv6 is configured and reachable at 2606:4700:7::a29f:872a, 2606:4700:7::a29f:862a

Got: 1 ms connect

IPv6 Ready

AAAA Records 2606:4700:7::a29f:872a, 2606:4700:7::a29f:862a Connection Reachable (1 ms)

A+

Crawlability

robots.txt present, sitemap with 21 URLs

PASS

robots.txt present, sitemap with 21 URLs

robots.txt is present

Got: 388 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 21 entries

Sitemap index with 21 child sitemaps

robots.txt does not reference a 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 388 B Sitemaps referenced 0 User-agents *, BLEXBot, bingbot Blocking No — crawling allowed

User-Agent: *
Disallow: /out/
Disallow: /category/home-featured-posts/
Disallow: /category/featured-extras/
Disallow: /category/love-letters/
Disallow: /2for20/
Disallow: /20bucks/
Disallow: /freebie/
Disallow: /freegift/
Disallow: /getonefree/
Disallow: /halfprice/
Disallow: /lastminutegift/
Disallow: /?blackhole

User-agent: BLEXBot
Crawl-delay: 10
User-agent: bingbot
Crawl-delay: 10

sitemap.xml 200 OK

Type Sitemap Index URLs 21 entries Valid XML Yes

Child Sitemaps:

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.Funnytimes.com/

200https://Funnytimes.com/

Preferred variant: non-www

HTTP → HTTPS

301http://Funnytimes.com/ → https://funnytimes.com/

Consistent

A+

Domain Intelligence

Funnytimes.com — via Tucows Domains Inc., 31 years, 7 months old

PASS

Funnytimes.com — via Tucows Domains Inc., 31 years, 7 months old

Domain registered until Feb 27, 2028 (1 years, 9 months remaining)

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.

Registrar: Tucows Domains Inc.

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

653 days

February 27, 2028

SSL certificate

87 days

Issued by Google Trust Services

Domain age

31 years, 7 months

Registered February 26, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:7::a29f:872a

Registrar

Tucows Domains Inc.

Unlocked 2 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 Tucows Domains Inc.

Created February 26, 1995 (31 years, 7 months ago)

Expires February 27, 2028 (1 years, 9 months)

Last Updated September 12, 2022

Name Servers daisy.ns.cloudflare.com, mustafa.ns.cloudflare.com

DNSSEC Not enabled

Hosting

IP Address 2606:4700:7::a29f:872a

Data source: rdap (0.5s)

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

CDN & Delivery

Cloudflare (DYNAMIC)

PASS

Cloudflare (DYNAMIC)

Site is served via Cloudflare CDN (edge: GRU)

Got: cf-ray: 9f992347fa8f0b84-GRU

CDN cache status: DYNAMIC

CDN Detected: Cloudflare

Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f992347fa8f0b84-GRU

A+

CDN Cache Observability

Cache state: DYNAMIC

PASS

Cache state: DYNAMIC

CDN cache state observable via 1 header(s)

Got: cf-cache-status=DYNAMIC