Skip to main content

Security report for awi-ami.com

Aerospace Welding Minneapolis, Inc. · Transportation · United States

Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

59/100

Risk levelMedium

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

Aerospace Welding Minneapolis, Inc. (AWI) is a well-established company founded in 1993 specializing in the manufacturing and repair of general aviation aircraft exhaust systems and engine mounts. The company holds FAA certifications and offers a range of services including certified welding, precision machining, and sheet metal fabrication. Their market position is strong as a world leader in their niche, targeting aviation professionals and aircraft owners. The website reflects a medium-sized business with a professional online presence built on Magento CMS, featuring e-commerce capabilities and clear contact information. Technically, the website employs modern web technologies such as Magento 2, RequireJS, jQuery, and Bootstrap, with Cloudflare DNS and GoDaddy as the registrar. Performance and mobile optimization are good, though accessibility is basic. Security posture is solid with HTTPS enforced and CAPTCHA on login, but improvements are recommended in DNSSEC deployment, cookie security flags, and security headers. Privacy compliance is basic with privacy and terms pages present but lacking explicit cookie consent mechanisms. Overall, the security posture is adequate but could be enhanced by implementing additional security headers and improving cookie security. No critical vulnerabilities or WAF blocking were detected, allowing full content accessibility. The business credibility is high, supported by FAA certifications and transparent contact details. The website is safe for general audiences with no adult or questionable content. Strategic recommendations include enabling DNSSEC, enforcing secure cookie flags, adding comprehensive security headers, and implementing explicit cookie consent to improve privacy compliance and user trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 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

6 findings rated critical or high. Fix these first.

  1. 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 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';…

  2. GDPR outside view

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

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching awi-ami.com

This scan found 22 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. The full timeline opens with your unlock code.

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
82
Security headers
50
Email security
80
DNS health
70
Network security
20
GDPR outside view
53
Average
59

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 awi-ami.com, from OffSeq Breach.

Total records
8
Employees
0
Customers
8
Third parties
0
Weak passwords
13%

1 subdomain affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for awi-ami.com.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)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

AWI operates in the transportation sector, focusing on aerospace manufacturing and repair services. Their competitive advantage lies in FAA certifications and a long-standing reputation since 1993. The business model combines manufacturing, repair, and e-commerce sales of aircraft parts. Revenue streams likely include parts sales, repair services, and welding services. Target customers are aviation mechanics, aircraft owners, and general aviation industry participants. The company maintains a modest partnership ecosystem, with limited social media presence primarily on Facebook. Growth indicators include a comprehensive website with product catalogs and service information. Strategic observations suggest a focus on quality certifications and customer engagement through news, events, and resources sections.

Security posture

The website demonstrates a moderate to good security maturity level. HTTPS is enforced, and login forms use CAPTCHA to mitigate automated attacks. However, DNSSEC is not enabled, which is a missed opportunity for DNS security. Cookie configurations in scripts show the secure flag as false, which could expose cookies over insecure connections if HTTPS is not strictly enforced everywhere. Security headers like Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options are not explicitly present, reducing defense-in-depth. No incident response or vulnerability disclosure policies are found, indicating potential gaps in security governance. No exposed sensitive data or vulnerable libraries were detected. Overall, the security culture appears functional but could benefit from formalized policies and enhanced technical controls.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS integrity and security.
  2. Set the secure flag to true on all cookies to ensure they are only transmitted over HTTPS.
  3. Implement and verify security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Add an explicit cookie consent mechanism to comply with privacy regulations and improve user trust.
  5. Develop and publish a vulnerability disclosure policy and incident response plan to enhance security governance.

Contact details published on the site

Addresses
Legal name
Aerospace Welding Minneapolis, Inc.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Aerospace Welding Minneapolis, Inc.
Description
Aerospace Welding Minneapolis, (AWI) was established in 1993 and is a world leader in general aviation aircraft exhaust systems and engine mount repair. They provide certified welding, precision machining, sheet metal fabrication, and FAA PMA certified parts.
Key services
Aircraft exhaust system manufacturing and repair, Engine mount repair and overhaul, Certified welding services, Precision machining, Sheet metal fabrication, FAA PMA certified parts sales
Content quality
good
Branding
consistent

Technology

Stack
Magento 2, RequireJS, jQuery, Owl Carousel, Google Analytics, Cloudflare DNS
Frameworks
Magento, Bootstrap
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of CAPTCHA on login
  • Secure cookie configuration (though secure flag false in cookie config script)

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Marketing tools
LiveChat
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is professionally presented and relevant to aerospace welding and aircraft parts.
  3. Use of Magento CMS with modern frontend technologies.
  4. Presence of FAA certifications and clear contact information enhances trust.
  5. No explicit privacy or security policy pages beyond basic privacy and terms found.
  6. No visible security.txt or vulnerability disclosure policy.
  7. Social media presence limited to Facebook.
  8. No suspicious or malicious domains detected.
  9. Cookie consent mechanism is not explicit despite cookie policy presence.
Technical notes

Notes

The website is built on Magento 2, leveraging RequireJS, jQuery, and Bootstrap for frontend functionality. It uses Cloudflare for DNS and GoDaddy as the domain registrar. The site includes Google Analytics and Google Tag Manager for tracking and marketing. Performance is moderate with responsive design and mobile optimization rated good. Accessibility features are basic, with room for improvement. The site uses multiple external libraries and scripts, including Owl Carousel and LiveChat integration. No critical technical debt or deprecated technologies were detected, but security-related technical improvements are recommended. The site structure and navigation are clear and user-friendly, supporting a positive user experience.
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 awi-ami.com. 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 awi-ami.com.

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.