Infrastructure - https://northe.runasp.net 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/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 5.9.179.196 does not match any cert SAN: w15.eu.machineasp.net

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

85 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

85

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
Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy

C

CDN & Delivery

Action

Assets on Fastly (host images.unsplash.com, 31 assets); document served directly from origin (Hetzner)

REVIEW

Assets on Fastly (host images.unsplash.com, 31 assets); document served directly from origin (Hetzner)

Document not behind existing CDN (Fastly serves the assets)

The page's subresources are delivered by Fastly (images.unsplash.com, 31 assets), but the HTML document itself comes straight from the origin (Hetzner). Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.

Got: delegation dualstack.com.imgix.map.fastly.net

Assets on Fastly: images.unsplash.com (assets: 31), cache HIT, HIT

Got: delegation dualstack.com.imgix.map.fastly.net

Assets on a CDN, document is not: Fastly

Document origin Hetzner

Asset hosts on a CDN

images.unsplash.com — Fastly · assets: 31 · Cache Status: HIT, HIT

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

B

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

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

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

1 A records, 51 ms lookup

PASS

1 A records, 51 ms lookup

Resolves to 1 IPv4 address(es)

Got: 5.9.179.196

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

No NS records found

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: 51 ms

Got: 51 ms

A	5.9.179.196
AAAA	—
CNAME	—
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 51 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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 23ms across 3 resolvers (spread 29ms)

PASS

Mean 23ms across 3 resolvers (spread 29ms)

Cloudflare: 7ms

Got: 7ms via 1.1.1.1:53

Quad9: 26ms

Got: 26ms via 9.9.9.9:53

Google: 36ms

Got: 36ms via 8.8.8.8:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://northe.runasp.net

https://northe.runasp.net

540 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://northe.runasp.net	200	540 ms	HTTP/1.1	Microsoft-IIS/10.0

A+

Crawlability

robots.txt present, sitemap with 8 URLs

PASS

robots.txt present, sitemap with 8 URLs

robots.txt is present

Got: 198 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 8 entries

robots.txt references sitemap

robots.txt 200 OK

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

User-agent: *
Allow: /


Disallow: /checkout

Disallow: /cart

Disallow: /order-confirmation

Disallow: /account

Disallow: /login

Disallow: /signup


Sitemap: https://northe.pk/sitemap.xml

sitemap.xml 200 OK

Type URL Set URLs 8 entries Valid XML Yes

Sample URLs:

A

URL Variants

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

PASS

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

HTTP→HTTPS redirect is not permanent

Got: HTTP 307 Expected: 301 or 308 permanent redirect

www / non-www

https://www.northe.runasp.net/

200https://northe.runasp.net/

HTTP → HTTPS

307http://northe.runasp.net/ → https://northe.runasp.net/

Use a permanent redirect (301 or 308) instead of a temporary one

A+

Domain Intelligence

runasp.net — via Gransy, s.r.o., 3 years, 5 months old, hosted on Hetzner

PASS

runasp.net — via Gransy, s.r.o., 3 years, 5 months old, hosted on Hetzner

Domain registered until May 12, 2027 (7 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: Gransy, s.r.o.

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: Hetzner

Got: AS24940

Domain expiry

226 days

May 12, 2027

SSL certificate

85 days

Issued by Let's Encrypt

Domain age

3 years, 5 months

Registered May 12, 2023

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Hetzner

ASN AS24940

136.243.231.50

Registrar

Gransy, s.r.o.

Unlocked 3 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 Gransy, s.r.o.

Created May 12, 2023 (3 years, 5 months ago)

Expires May 12, 2027 (7 months)

Last Updated April 26, 2026

Name Servers ns1.machineasp.net, ns2.machineasp.net, ns3.machineasp.net

DNSSEC Not enabled

Hosting

IP Address 136.243.231.50

ASN AS24940 (HETZNER-AS - Hetzner Online GmbH, DE)

Provider Hetzner

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 551 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

54 ms

TCP Connect

156 ms

TLS Handshake

171 ms

Time to First Byte

551 ms

Total Time

551 ms

Connection waterfall

DNS Lookup 54 ms TCP Connect 156 ms TLS Handshake 171 ms Server Processing 170 ms Content Transfer 1 ms

A+

Health Check Endpoint

Health endpoint at https://northe.runasp.net/health (HTTP 200)

PASS

Health endpoint at https://northe.runasp.net/health (HTTP 200)

Public health endpoint at https://northe.runasp.net/health

Got: https://northe.runasp.net/health