Skip to main content

Security report for howlwiththewolves.ca

Other · N/a

Medium risk. 8 critical or high findings in Email security, Security headers and 2 other checks.

Security score

63/100

Risk levelMedium

0–100, higher is better. How it is calculated

The website howlwiththewolves.ca is currently inaccessible, presenting a 403 error page generated by AWS CloudFront, indicating that the request is blocked likely due to a Web Application Firewall (WAF) or configuration error. As a result, no business content, metadata, or contact information is available for analysis. The domain is newly registered in March 2024 with privacy protection enabled, limiting the ability to verify registrant details or business legitimacy. Hosting is provided via Amazon AWS CloudFront CDN, but no further technical or security details can be extracted due to the blocked content. From a security perspective, the lack of accessible content and security headers prevents a thorough evaluation of the website's security posture. The domain does not have DNSSEC enabled, which is a recommended security enhancement. No privacy, cookie, or terms of service policies are found, indicating potential compliance gaps. No contact or incident response information is available, reducing transparency and trust. Overall, the website's risk profile is elevated due to the absence of accessible content and transparency. The new domain age combined with privacy-protected WHOIS data and blocked content suggests caution. Strategic recommendations include resolving the WAF or configuration issues to allow content access, implementing standard security headers and HTTPS enforcement, publishing privacy and cookie policies, and providing clear contact and incident response information to improve trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

8 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  3. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

Need hands-on remediation? Email guard@offseq.com

Keep watching howlwiththewolves.ca

This scan found 24 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
77
Security headers
15
Email security
60
DNS health
75
Network security
100
GDPR outside view
50
Average
63

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention howlwiththewolves.ca, from OffSeq Breach.

No leaked records found

Breach holds no records for howlwiththewolves.ca right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Due to the lack of accessible website content and metadata, no meaningful business intelligence can be derived. The domain is newly registered and privacy protected, which is common for startups or small businesses but limits visibility into market positioning, business model, or services. No social media or partner domains are linked. The absence of business information and contact details suggests the website is either under development or improperly configured.

Security posture

The current security posture cannot be fully assessed due to the blocked website content. The domain uses AWS CloudFront CDN, which provides robust infrastructure and WAF capabilities. However, DNSSEC is not enabled, and no security headers or HTTPS details are available. The 403 error indicates active WAF rules or misconfiguration blocking access. No vulnerability disclosures, incident response contacts, or security policies are published. The domain registration includes privacy protection, which is neutral but reduces transparency. Overall, the security maturity appears low due to lack of visible security best practices and transparency.

Recommendations

  1. Resolve CloudFront WAF or configuration issues to restore website accessibility.
  2. Enable DNSSEC on the domain to enhance DNS security.
  3. Implement and enforce HTTPS with proper SSL/TLS configuration.
  4. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Publish comprehensive privacy, cookie, and terms of service policies to improve compliance and user trust.
  6. Provide clear contact information including incident response and abuse contacts.
  7. Conduct a security audit to identify and remediate any misconfigurations or vulnerabilities.
  8. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  9. Improve website content quality and branding consistency once accessibility is restored.
  10. Consider removing WHOIS privacy protection if transparency is a priority for business credibility.
Site observations

Automated reading of the public site. Ratings are indicative.

CloudFront detected. The page is a 403 error generated by AWS CloudFront indicating request blocked due to WAF or configuration issues. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Analytics and tracking

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is inaccessible due to a CloudFront 403 error page.
  2. No metadata, structured data, or business content available for analysis.
  3. No contact information, policies, or security disclosures found.
  4. Domain is newly registered with privacy protection.
  5. Hosting uses AWS CloudFront CDN.
  6. No evidence of tracking, analytics, or advertising scripts.
  7. Content safety is rated safe due to lack of content.
  8. Analysis is incomplete due to WAF/security blocking.
Technical notes

Notes

The website is hosted behind Amazon AWS CloudFront CDN, which provides scalable and secure content delivery. The domain uses multiple AWS name servers but does not have DNSSEC enabled, which is a recommended security enhancement. Due to the 403 error page, no HTML metadata, scripts, or CMS information can be extracted. There is no evidence of analytics, advertising, or tracking technologies. The website appears to be either under development or misconfigured, resulting in blocked access. Performance, mobile optimization, accessibility, and SEO cannot be assessed. The technical debt and modernization opportunities cannot be evaluated without content access.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with howlwiththewolves.ca. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review howlwiththewolves.ca.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.