The website yottlyscript.com currently serves no accessible content, returning a 404 error page indicating the requested resource could not be found. There is no metadata, structured data, or business information available on the site. The domain is registered with GoDaddy.com, LLC since 2015 and is not privacy protected, which suggests some level of legitimacy. However, the lack of any visible content or contact information severely limits the ability to assess the business or its market position. Technically, the site lacks security headers and DNSSEC is not enabled, indicating a basic security posture. Overall, the site appears inactive or under development, with minimal digital maturity and poor user experience.
a(a) Risk analysis and security policies: Not visible from outside
b(b) Incident handling: One indicator
c(c) Business continuity, backups and crisis management: Not visible from outside
d(d) Supply chain security: Not visible from outside
e(e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
f(f) Assessing the effectiveness of security measures: Not visible from outside
g(g) Cyber hygiene and security training: Not visible from outside
h(h) Cryptography and encryption: Partly checked
i(i) HR security, access control and asset management: One indicator
j(j) Multi-factor authentication and secured communications: Not visible from outside
Partly checked
One indicator
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.
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
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"
This scan found 25 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.
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
40
GDPR outside view
40
Average
51
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 yottlyscript.com, from OffSeq Breach.
No leaked records found
Breach holds no records for yottlyscript.com right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Business context
Business profile
Due to the absence of any business-related content, no insights into market positioning, business model, revenue streams, or partnerships can be derived. The domain age suggests the business could be established, but no supporting evidence is present on the website. No contact details or trust indicators are available to validate the business operations or credibility.
Security posture
The security posture is minimal. The domain uses HTTPS (implied by URL scheme), but no security headers are detected and DNSSEC is not enabled. There are no visible vulnerabilities or exposed sensitive data due to lack of content. No incident response or security policies are published. The site would benefit from implementing standard security best practices and transparency measures to improve trustworthiness.
Recommendations
Develop and publish actual website content to provide business information and improve user experience.
Implement and publish privacy and cookie policies to comply with GDPR and other regulations.
Add contact information including emails, phone numbers, and physical addresses to enhance credibility.
Enable DNSSEC and configure security headers such as Content-Security-Policy and Strict-Transport-Security.
Conduct a security audit and implement incident response and vulnerability disclosure policies.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
Content quality
poor
Branding
inconsistent
Technology
Performance
moderate
Mobile
poor
Accessibility
poor
SEO
poor
Security
Observed score
30/100
Analytics and tracking
Tracking level
minimal
Privacy practices
poor
Advertising
Transparency
poor
Site quality
Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low
Key observations
Website content is inaccessible beyond a 404 error page.
No metadata, structured data, or SEO elements found.
No forms, contact information, or social media links present.
No security headers detected and DNSSEC is not enabled.
Domain is registered with GoDaddy and is not privacy protected.
No privacy, cookie, or terms of service policies found.
No evidence of advertising, analytics, or tracking technologies.
Website appears inactive or under construction with no business information.
Technical notes
Notes
The website currently serves only a minimal HTML page with a 404 error message and no metadata or scripts. The domain is hosted via GoDaddy.com, LLC. No CMS or frameworks are detected. The site lacks mobile optimization, accessibility features, and SEO elements. Performance cannot be fully assessed due to lack of content but is likely moderate given minimal resources. The technical infrastructure requires modernization and proper configuration to support a functional and secure website.
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.
Reviews of this site
Share your experience with yottlyscript.com. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review yottlyscript.com.