Infrastructure
· 9 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.
BRedirect Chain1 redirect(s), 1483 ms totalREVIEW
https://no-ip.com
630 ms · HTTP/1.1
https://www.noip.com/
853 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://no-ip.com | 301 | 630 ms | HTTP/1.1 | nginx |
| 2 | https://www.noip.com/ | 200 | 853 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
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 & Recommendations328 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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
A+DNS Records1 A records, 32 ms lookupPASS
| A | 158.247.7.199 |
| AAAA | — |
| CNAME | — |
| NS | ns3.no-ip.com, ns1.no-ip.com, ns4.no-ip.com, ns2.no-ip.com |
| MX | 5 mail0.no-ip.com 10 mail1.no-ip.com 15 mail2.no-ip.com |
| TXT | 202303220843062ywbypmqyuext265di36he6ylwieojs6uddfn6emx2nw1ev8f4 SPF v=spf1 ip4:8.23.224.0/24 ip4:158.247.6.0/23 ip4:69.65.5.96/27 include:_spf.hoste... n915fvn5p8m2s6pqk2bhyr94kz5ymdpt _t2k10tgfljrhaodhuy5gtemiw0dkklb |
| 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
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Crawlabilityrobots.txt present, sitemap with 81 URLsPASS
User-agent: *
Allow: /
Disallow: /hostactive
Disallow: /hostactive.php
Disallow: /pt-BR/hostactive
Disallow: /pt-BR/hostactive.php
Disallow: /confirm-host
Disallow: /it-IT/confirm-host
Disallow: /pt-BR/confirm-host
Disallow: /confirm-account
Disallow: /it-IT/confirm-account
Disallow: /pt-BR/confirm-account
Disallow: /confirm
Disallow: /it-IT/confirm
Disallow: /pt-BR/confirm
Disallow: /confirm-email-change
Disallow: /resent-activation
Disallow: /reactivate-account
Disallow: /members
Disallow: /sign-up?t=*
Sitemap: https://www.noip.com/sitemap.xml
Sitemap: https://www.noip.com/support/sitemap_index.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceno-ip.com — via No-IP Technologies, LLC, 26 years, 11 months old, hosted on NOIP-VITAL - Vitalwerks Internet Solutions, LLC, USPASS
84 days
October 4, 2026
328 days
Issued by DigiCert Inc
26 years, 11 months
Registered October 4, 1999
Not enabled
Protects against DNS spoofing
NOIP-VITAL - Vitalwerks Internet Solutions, LLC, US
ASN AS14627
158.247.7.199
No-IP Technologies, LLC
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- 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