Skip to main content

Security report for dorianlpg.com

Dorian LPG Ltd · Energy · United States

Medium risk. 4 critical or high findings in Security headers and SSL/TLS.

Security score

74/100

Risk levelMedium

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

Dorian LPG Ltd is a leading liquefied petroleum gas shipping company specializing in the ownership and operation of very large gas carriers (VLGCs). With a global footprint including offices in the United States, Greece, and Denmark, the company plays a critical role in transporting LPG to support the world's energy transition. The website serves primarily as an investor relations portal, providing comprehensive financial reports, ESG disclosures, and corporate governance information. The company is publicly traded on the NYSE under the ticker LPG, reinforcing its market credibility and transparency. Technically, the website is built on a mature ASP.NET WebForms platform integrated with Q4 Inc's investor relations tools, leveraging modern JavaScript libraries such as jQuery, Splide.js, and DataTables for enhanced user experience. The site demonstrates good mobile optimization, accessibility, and SEO practices, with a moderate performance profile. Security measures include HTTPS enforcement, Content Security Policy headers, anti-CSRF tokens, and Google reCAPTCHA integration, reflecting a solid security posture. No critical vulnerabilities or WAF blocks were detected, and the domain registration details align well with the company's public profile, indicating legitimacy and trustworthiness. Privacy and cookie policies are present and comprehensive, with active consent mechanisms, supporting GDPR compliance. However, explicit security policies, incident response contacts, and terms of service pages are absent, representing areas for improvement. Overall, the website is professional, secure, and well-suited for its investor relations purpose, though enhancements in security transparency and contact information could further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
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

4 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. 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
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching dorianlpg.com

This scan found 19 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
57
Security headers
35
Email security
85
DNS health
85
Network security
100
GDPR outside view
83
Average
74

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

Total records
136
Employees
1
Customers
21
Third parties
114
Weak passwords
8%

Latest record dated 2025-04-15 · 4 subdomains 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 dorianlpg.com.

Select it in the checkout above.

Masked preview

  • –support.dorianlpg.com2025-04-15

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

Technical appendix

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

Business context

Business profile

Dorian LPG Ltd occupies a strong market position as a specialized owner and operator of VLGCs in the energy transportation sector. Its business model focuses on safe, reliable, and environmentally conscious shipping of LPG, aligning with global energy transition trends. The company targets investors, industry partners, and customers requiring large-scale LPG transportation. Revenue streams likely derive from chartering its fleet and related shipping services. The website's comprehensive financial disclosures and ESG reporting indicate a mature governance and compliance framework. The presence of multiple offices across key regions suggests a geographically diversified operational footprint. The company leverages partnerships with Q4 Inc for digital investor engagement and uses social media channels to enhance brand visibility. Strategic observations include a focus on sustainability, operational excellence, and transparent investor communications, positioning Dorian LPG as a credible and forward-looking player in its niche.

Security posture

The website exhibits a mature security posture with HTTPS enforced site-wide, Content Security Policy headers, and anti-CSRF protections on forms. Google reCAPTCHA v2 invisible is implemented to mitigate automated abuse on subscription forms. The domain is registered without privacy protection, with standard registrar locks enhancing domain security. No exposed sensitive data or vulnerable libraries were detected in the analyzed content. However, the absence of explicit security policies, incident response contacts, and vulnerability disclosure mechanisms limits transparency and may impact incident readiness. The use of multiple third-party scripts and analytics tools introduces a moderate tracking footprint, balanced by clear cookie and privacy policies with consent mechanisms. Overall, the security posture is strong but could be improved by publishing dedicated security and incident response information and enabling DNSSEC.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish a dedicated security policy and incident response contact information to improve transparency and readiness.
  3. Add a vulnerability disclosure or security.txt file to facilitate responsible reporting of security issues.
  4. Implement additional security headers such as HSTS, X-Frame-Options, and X-Content-Type-Options for enhanced protection.
  5. Regularly audit and update third-party scripts and libraries to mitigate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Dorian LPG Ltd
Description
Dorian LPG is a liquefied petroleum gas shipping company and a leading owner and operator of modern very large gas carriers (VLGCs). The company operates globally with offices in Connecticut, USA, Athens, Greece, and Copenhagen, Denmark.
Key services
VLGC shipping, Fleet management, Safety and operational excellence, Investor relations and financial reporting
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery, Splide.js, DataTables, Google reCAPTCHA, Q4 Inc widgets and APIs, Fancybox, Slick Carousel
Frameworks
ASP.NET WebForms
Platforms
Q4 Inc Investor Relations Platform
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Content Security Policy implemented
  • Google reCAPTCHA v2 invisible used on forms
  • Anti-CSRF tokens present
  • Form validation implemented

Analytics and tracking

Services
Google Analytics, New Relic
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Google Ad Services
Marketing tools
Pendo, New Relic, BugHerd
Transparency
good

Site quality

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

Key observations

  1. Website is professionally designed and well-structured for investor relations.
  2. Comprehensive financial and ESG reporting available.
  3. Strong presence of security best practices and privacy compliance.
  4. No critical security issues or WAF blocking detected.
  5. Use of multiple third-party services for analytics, marketing, and investor tools.
  6. No explicit security policy or incident response contact found.
  7. No terms of service page detected.
  8. Contact information primarily via forms and email alerts; no explicit phone numbers or physical addresses found in the content.
Technical notes

Notes

The website is built on ASP.NET WebForms integrated with Q4 Inc's investor relations platform, utilizing modern JavaScript libraries including jQuery, Splide.js for sliders, DataTables for responsive tables, and Fancybox for media overlays. Google reCAPTCHA is used for bot mitigation on forms. The site loads resources from multiple trusted CDNs and Q4 Inc domains, indicating a robust content delivery strategy. Performance is moderate, with good mobile responsiveness and accessibility features implemented. SEO is supported by proper meta tags and structured navigation. The technical stack reflects a balance between legacy ASP.NET technology and modern front-end enhancements, suitable for the site's investor relations focus. Opportunities exist to modernize further and optimize performance, but current infrastructure supports business needs effectively.
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 dorianlpg.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 dorianlpg.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.