Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
BReverse DNS0/2 IPs match cert SANREVIEW
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations82 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
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
BCDN & DeliveryNetlifyREVIEW
BOperational Status PageNo status page link detectedREVIEW
BHealth Check EndpointNo conventional health endpoint foundREVIEW
A+DNS Records2 A records, 2 ms lookupPASS
| A | 35.157.26.135, 63.176.8.218 |
| AAAA | — |
| CNAME | — |
| NS | dns2.p03.nsone.net, dns1.p03.nsone.net, dns4.p03.nsone.net, dns3.p03.nsone.net |
| MX | — |
| TXT | google-site-verification=iW6HiZTru9HLvTVASIFypiizkPrk7saCmxCLDqyodmg |
| CAA | Lookup not available with standard resolver |
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
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 TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 23ms across 3 resolvers (spread 18ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://nomicalc.com
227 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://nomicalc.com | 200 | 227 ms | HTTP/1.1 | Netlify |
A+Crawlabilityrobots.txt present, sitemap with 31 URLsPASS
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$
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencenomicalc.com — via Name.com, Inc., 1 years old, hosted on AWSPASS
359 days
July 16, 2027
82 days
Issued by Let's Encrypt
1 years
Registered July 16, 2025
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
63.176.8.218
Name.com, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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