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
CReverse DNSAction0/2 IPs match cert SANREVIEW
BMulti-Resolver DNS SpeedMean 49ms across 3 resolvers (spread 100ms)REVIEW
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 & Recommendations156 days until leaf cert expires — 5 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
- 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
BOperational Status PageNo status page link detectedREVIEW
BHealth Check EndpointNo conventional health endpoint foundREVIEW
ADNS Records2 A records, 352 ms lookupPASS
| A | 76.66.216.136, 67.210.219.20 |
| AAAA | — |
| CNAME | — |
| NS | ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info |
| MX | 0 cust79003-1.in.mailcontrol.com 1 cust79003-2.in.mailcontrol.com |
| TXT | cisco-ci-domain-verification=ac499827b29e4994eac71c6a9476da5a2cdb8d9eb625092ddf0... SPF v=spf1 ip4:69.46.126.197 ip4:67.210.219.11 ip4:76.66.216.144 ip4:65.110.174.168 ... Dynatrace-site-verification=6016265a-b5a3-413a-a2fd-bad92df28701__40mksngi9me5lo... docusign=57161bc3-75a2-4d64-93aa-b8cbb5e343ee MS=ms70141317 mjerNQeBuptuTSqxopylVS/s/O6JgNkVNPOa1hs8b5xl1v1mFt/cfWdd0oeiB4mA+obaJhgfGWWjejnG... google-site-verification=Xiyd0KUKeqctcwYzT0997ZYkvj9WO0zskjf11uIHhWM apple-domain-verification=ulHvmEGvm3eHBdqr docusign=67ab69dd-1792-41c1-9a01-225ed0f19524 adobe-idp-site-verification=b70b58a2fa79357572d1e589e7e494194848fcc092845819e063... canva-site-verification=IXbyYhqpD-ogLd5pjRwJGg atlassian-domain-verification=HqOMSWo3OOVpXMqLHStmA8D5f8zaCvCCgW38kbO1SszAeSEaj9... bd1dbf1b-e60c-4242-82a6-e2b318802cde miro-verification=48391439390e484486db81352237095b4027182f spacelift-domain-verification=hifu39d7 flexera-domain-verification-uiekevudxhzvsnwp openai-domain-verification=dv-uH63tbyAc2KCWIxWo90L1ris astro-domain-verification=cmebfeno40ber01l5hwjotj14 cursor-domain-verification-ar515x=1Djq3KYvV89zAK3Bb21g3wdX5 anthropic-domain-verification-z70wcq=RPJHRIML1WBPRqELluaWW0kQB Dynatrace-site-verification=cd441d92-4c96-45bb-8c40-4281cfbaf757__am4veuh9lj3egn... |
| CAA | Lookup not available with standard resolver |
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
ARedirect Chain1 redirect(s), 328 ms totalPASS
https://otpp.com
119 ms · HTTP/1.1
https://otpp.com/en-ca/
209 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://otpp.com | 302 | 119 ms | HTTP/1.1 | |
| 2 | https://otpp.com/en-ca/ | 200 | 209 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
A+Crawlabilityrobots.txt present, sitemap with 1991 URLsPASS
User-agent:*
#Crawl sitemaps
Sitemap:https://www.otpp.com/sitemap.xml
# Algolia-Crawler-Verif: D38A2B092298F41B
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceotpp.com — via Network Solutions, LLC, 29 years, 7 months old, hosted on BACOM - Bell Canada, CAPASS
1387 days
March 14, 2030
156 days
Issued by DigiCert Inc
29 years, 7 months
Registered March 13, 1997
Not enabled
Protects against DNS spoofing
BACOM - Bell Canada, CA
ASN AS577
76.66.216.136
Network Solutions, LLC
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