Skip to content
https://nerginc.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
9
PASS
8
INFO
0
Probed from Madrid, Spain
308 Permanent Redirect
Checks
17
8 PASS 9 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
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)
Info::
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/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 216.198.79.1: lookup 216.198.79.1: 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.
Info::
PTR lookup failed for 64.29.17.1: lookup 64.29.17.1: 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.
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 redirects to HTTPS permanently
Got: HTTP 308

www / non-www

200https://www.nerginc.com/
200https://nerginc.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

308http://nerginc.com/ → https://nerginc.com/

Consistent

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

Certificate validity

88
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
Vercel
REVIEW
Vercel
Info::
Document is served via Vercel CDN
Got: x-vercel-id: cdg1::tdjjx-1793248684005-738a9ef7523c
Document served via CDN: Vercel
Provider Vercel Evidence x-vercel-id: cdg1::tdjjx-1793248684005-738a9ef7523c
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
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, 38 ms lookup
PASS
2 A records, 38 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 216.198.79.1, 64.29.17.1
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: kellen.ns.cloudflare.com, ximena.ns.cloudflare.com
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 38 ms
Got: 38 ms
A216.198.79.1, 64.29.17.1
AAAA—
CNAME—
NSkellen.ns.cloudflare.com, ximena.ns.cloudflare.com
MX
89 route3.mx.cloudflare.net
95 route1.mx.cloudflare.net
96 route2.mx.cloudflare.net
TXT
SPF v=spf1 include:_spf.mx.cloudflare.net ~all
CAALookup not available with standard resolver
Resolved in 38 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 25ms across 3 resolvers (spread 41ms)
PASS
Mean 25ms across 3 resolvers (spread 41ms)
Info::
Quad9: 0ms
Got: 0ms via 9.9.9.9:53
Info::
Cloudflare: 35ms
Got: 35ms via 1.1.1.1:53
Info::
Google: 41ms
Got: 41ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 245 ms total
PASS
1 redirect(s), 245 ms total
Info::
Single redirect
Got: https://nerginc.com → https://www.nerginc.com/ (308)
Info::
WWW normalization redirect

https://nerginc.com

182 ms · HTTP/1.1

308

https://www.nerginc.com/

63 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nerginc.com308182 msHTTP/1.1Vercel
2https://www.nerginc.com/20063 msHTTP/1.1Vercel

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 64 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 64 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Sitemap: https://nerginc.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 4 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
nerginc.com — via Cloudflare, Inc., 1 days old, hosted on AWS
PASS
nerginc.com — via Cloudflare, Inc., 1 days old, hosted on AWS
Info::
Domain registered until Oct 27, 2027 (1 years remaining)
Info::
Domain is only 1 days old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Oct 27, 2026
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: Cloudflare, 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: AWS
Got: AS16509
Domain expiry

353 days

October 27, 2027

SSL certificate

88 days

Issued by Let's Encrypt

Domain age

1 days

Registered October 27, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

216.198.79.1

Registrar

Cloudflare, 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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc.
Created October 27, 2026 (1 days ago)
Expires October 27, 2027 (1 years)
Last Updated October 27, 2026
Name Servers kellen.ns.cloudflare.com, ximena.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 216.198.79.1
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.1s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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

Connection waterfall

DNS Lookup 48 ms TCP Connect 1 ms TLS Handshake 41 ms Server Processing 211 ms Content Transfer 0 ms
A+
Health Check Endpoint
Health endpoint at https://nerginc.com/health (HTTP 200)
PASS
Health endpoint at https://nerginc.com/health (HTTP 200)
Info::
Public health endpoint at https://nerginc.com/health
Got: https://nerginc.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback