Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BReverse DNS0/1 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 & Recommendations75 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- 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 Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
ADNS Records1 A records, 44 ms lookupPASS
| A | 208.115.251.74 |
| AAAA | — |
| CNAME | ndmnet.eu |
| NS | ian.ns.cloudflare.com, raina.ns.cloudflare.com |
| MX | 0 mail.ndmnet.eu |
| TXT | SPF v=spf1 ip4:85.195.73.202 ip4:198.46.143.182 ip4:23.94.209.142 include:relay.mail... |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+CAA Recordsissue: comodoca.com, digicert.com, letsencrypt.org, pki.goog, ssl.com | issuewild: comodoca.com, digicert.com, letsencrypt.org, pki.goog, ssl.com | iodef configuredPASS
A+Multi-Resolver DNS SpeedMean 19ms across 3 resolvers (spread 29ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://www.ndmnet.eu
77 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.ndmnet.eu | 200 | 77 ms | HTTP/1.1 | LiteSpeed |
A+Crawlabilityrobots.txt present, sitemap with 10 URLsPASS
User-agent: *
Allow: /
Disallow: /beta/
Disallow: /status/
Disallow: /form-result.php
Sitemap: https://www.ndmnet.eu/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligencendmnet.eu — via SupportHost OÜ, hosted on LIMESTONENETWORKS - Limestone Networks, Inc., USPASS
Unknown
75 days
Issued by Let's Encrypt
Unknown
Status unknown
Protects against DNS spoofing
LIMESTONENETWORKS - Limestone Networks, Inc., US
ASN AS46475
208.115.251.74
SupportHost OÜ