Infrastructure - https://nomicalc.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.

B

Reverse DNS

0/2 IPs match cert SAN

REVIEW

0/2 IPs match cert SAN

PTR for 13.52.188.95 does not match any cert SAN: ec2-13-52-188-95.us-west-1.compute.amazonaws.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

PTR for 52.52.192.191 does not match any cert SAN: ec2-52-52-192-191.us-west-1.compute.amazonaws.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

82 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

82

days left

0d 30d 60d 90d+

Recommended actions

Add includeSubDomains to the HSTS directive
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

B

CDN & Delivery

Netlify

REVIEW

Netlify

Site is served via Netlify CDN

Got: x-nf-request-id: 01KXZPXJR99H3PNK5JNPGDF8D2

CDN Detected: Netlify

Provider Netlify Evidence x-nf-request-id: 01KXZPXJR99H3PNK5JNPGDF8D2

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.

A+

DNS Records

2 A records, 13 ms lookup

PASS

2 A records, 13 ms lookup

Resolves to 2 IPv4 address(es)

Got: 13.52.188.95, 52.52.192.191

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net

No MX records — email not configured via DNS

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution time: 13 ms

Got: 13 ms

A	13.52.188.95, 52.52.192.191
AAAA	—
CNAME	—
NS	dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net
MX	—
TXT	google-site-verification=iW6HiZTru9HLvTVASIFypiizkPrk7saCmxCLDqyodmg
CAA	Lookup not available with standard resolver

Resolved in 13 ms

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Multi-Resolver DNS Speed

Mean 20ms across 3 resolvers (spread 37ms)

PASS

Mean 20ms across 3 resolvers (spread 37ms)

Quad9: 8ms

Got: 8ms via 9.9.9.9:53

Cloudflare: 8ms

Got: 8ms via 1.1.1.1:53

Google: 45ms

Got: 45ms via 8.8.8.8:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://nomicalc.com

https://nomicalc.com

98 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://nomicalc.com	200	98 ms	HTTP/1.1	Netlify

A+

Crawlability

robots.txt present, sitemap with 31 URLs

PASS

robots.txt present, sitemap with 31 URLs

robots.txt is present

Got: 506 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 31 entries

robots.txt references sitemap

robots.txt 200 OK

Size 506 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

User-agent: *
Allow: /

# Sitemap
Sitemap: https://nomicalc.com/sitemap.xml

# Disallow admin or private areas
Disallow: /auth
Disallow: /api/
Disallow: /admin/
Disallow: /smart-redirect

# Allow important public pages (Allow: / ya cubre todo)
Allow: /quienes-somos
Allow: /legal
Allow: /blog
Allow: /favicon.ico
Allow: /favicon-48x48.png
Allow: /favicon-96x96.png
Allow: /assets/

# Additional SEO directives
Allow: /public/

# Keep JS/CSS crawlable so Google can render pages correctly.
Disallow: /*.map$

sitemap.xml 200 OK

Type URL Set URLs 31 entries Valid XML Yes

Sample URLs:

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.nomicalc.com/

200https://nomicalc.com/

Preferred variant: non-www

HTTP → HTTPS

301http://nomicalc.com/ → https://nomicalc.com/

Consistent

A+

Domain Intelligence

nomicalc.com — via Name.com, Inc., 1 years old, hosted on AWS

PASS

nomicalc.com — via Name.com, Inc., 1 years old, hosted on AWS

Domain registered until Jul 16, 2027 (1 years 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: Name.com, 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.

Hosting: AWS

Got: AS16509

Domain expiry

359 days

July 16, 2027

SSL certificate

82 days

Issued by Let's Encrypt

Domain age

1 years

Registered July 16, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.52.188.95

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 July 16, 2025 (1 years ago)

Expires July 16, 2027 (1 years)

Last Updated June 14, 2026

Name Servers dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net

DNSSEC Not enabled

Hosting

IP Address 13.52.188.95

ASN AS16509 (AMAZON-02 - 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 405 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

14 ms

TCP Connect

3 ms

TLS Handshake

71 ms

Time to First Byte

402 ms

Total Time

405 ms

Connection waterfall

DNS Lookup 14 ms TCP Connect 3 ms TLS Handshake 71 ms Server Processing 314 ms Content Transfer 3 ms

A+

CDN Cache Observability

Cache state: fresh (Age=0)

PASS

Cache state: fresh (Age=0)

CDN cache state observable via 1 header(s)

Got: age=0

A+

Health Check Endpoint

Health endpoint at https://nomicalc.com/health (HTTP 200)

PASS

Health endpoint at https://nomicalc.com/health (HTTP 200)

Public health endpoint at https://nomicalc.com/health

Got: https://nomicalc.com/health