myworkpay.com Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of myworkpay.com on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 30106ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 125 KB, and the site is served behind a CDN (Content Delivery Network).
Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted.
The security headers analysis reveals a score of 55/100 (moderate). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), and X-Frame-Options. However, the site is missing X-Content-Type-Options, Referrer-Policy, and Permissions-Policy, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks.
Our technology detection scan identified 12 technologies across 11 categories powering myworkpay.com. The detected stack includes Webflow, Vite, Google Analytics 4, Hotjar 3469042, Google Tag Manager, Twitter Pixel, Intercom, HubSpot, Amazon CloudFront, Google Fonts, YouTube Embed, and jQuery 3.5.1..
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, myworkpay.com receives an overall trust score of 72/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time30106ms
ProtocolHTTP/2
Page Size125 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Servercloudflare
Total Requests370
3rd Party Domains26
Redirect2 hop(s)
Detected Technologies (12)
• Webflow
🔨 Vite
📊 Google Analytics 4
📊 Hotjar
🏷️ Google Tag Manager
📢 Twitter Pixel
💬 Intercom
📣 HubSpot
☁️ Amazon CloudFront
🔤 Google Fonts
🎬 YouTube Embed
📦 jQuery
Security Headers
✓
Content-Security-Policy
Set ✓
✓
Strict-Transport-Security (HSTS)
Set ✓
✗
X-Content-Type-Options
Not set
✗
Referrer-Policy
Not set
✗
Permissions-Policy
Not set
SSL Certificate
IssuerGoogle Trust Services
Issuer FullcountryName=US, organizationName=Google Trust Services, commonName=WE1
SubjectcommonName=myworkpay.com
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
myworkpay.com Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, myworkpay.com receives a trust score of 72/100, which places it in the "Likely Safe" category. This score is calculated by evaluating multiple factors including SSL certificate validity, domain registration history, email authentication protocols, security header configuration, and blacklist status across major threat intelligence databases.
The analysis identified several positive trust signals: a valid HTTPS connection protecting data in transit, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification.
Areas of concern include: missing Referrer-Policy, potentially leaking URL information to third parties, the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity, and DNSSEC is not enabled, leaving DNS queries vulnerable to spoofing attacks. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved.
We checked myworkpay.com against 8 major blacklist databases including Google Safe Browsing, Phishtank, Urlhaus, Openphish, Dnsfilter, Spamhaus Dbl, Surbl, and Virustotal. The domain passed all 8 checks with a clean status, meaning it has not been flagged for phishing, malware distribution, spam, or other malicious activities by any of the tested threat intelligence providers.
Trust Signals
✅ Valid HTTPS
✅ HSTS enabled
✅ SPF configured
✅ DMARC configured (p=reject)
✅ DKIM configured
⚠️ DNSSEC not enabled
✅ Sitemap.xml found
✅ Robots.txt found
⚠️ Missing Referrer-Policy
Blacklist Checks (8/8 clean)
✓
Google Safe Browsing
clean
✓
Phishtank
clean
✓
Urlhaus
clean
✓
Openphish
clean
✓
Dnsfilter
clean
✓
Spamhaus Dbl
clean
✓
Surbl
clean
✓
Virustotal
clean
myworkpay.com Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned myworkpay.com and identified 12 distinct technologies across 11 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records.
CMS: Webflow — manages the content and page structure for myworkpay.com.
Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for myworkpay.com.
Analytics: Google Analytics 4 and Hotjar (version 3469042) — tracks visitor behavior and provides traffic insights for myworkpay.com.
Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for myworkpay.com.
Advertising: Twitter Pixel — handles advertising pixel tracking and conversion measurement for myworkpay.com.
Chat: Intercom — provides live chat and customer communication for myworkpay.com.
Marketing: HubSpot — provides marketing automation capabilities for myworkpay.com.
CDN: Amazon CloudFront — accelerates content delivery by caching assets at edge locations worldwide for myworkpay.com.
Fonts: Google Fonts — delivers web fonts for typography for myworkpay.com.
Video: YouTube Embed — provides video hosting and playback for myworkpay.com.
JavaScript Library: jQuery (version 3.5.1.) — provides utility functions and DOM manipulation for myworkpay.com.
We also extracted the following tracking identifiers: Google Tag Manager container GTM-NTLVQPZ, Hotjar Site ID 3469042, and Intercom App ID jjzx1va4. These IDs can be used to identify other websites operated by the same organization.
CMS
Build Tool
Analytics
📊 Google Analytics 4(95%)📊 Hotjar 3469042(100%)
Tag Manager
🏷️ Google Tag Manager(95%)
Advertising
Chat
Marketing
CDN
☁️ Amazon CloudFront(95%)
Fonts
Video
JavaScript Library
Tracking IDs
gtm_idGTM-NTLVQPZ
hotjar_id3469042
intercom_app_idjjzx1va4
myworkpay.com Performance, Speed & Core Web Vitals
🤖 AI Summary
myworkpay.com delivers its homepage in 30106ms (server response time), which is considered slow by industry standards. The total page weight is 125 KB, and we detected 370 resource requests loading assets from 26 third-party domains. A high number of third-party domains can significantly impact page load time due to additional DNS lookups and TLS handshakes required for each domain.
The website uses Gzip compression for text-based assets, achieving an estimated 60.0% reduction in transfer size. This reduces bandwidth usage and improves page load times, especially for visitors on slower connections.
Asset minification status: 1 out of 4 CSS files and 1 out of 18 JavaScript files are minified. Minifying the remaining 20 unminified file(s) could further reduce page weight by 10-30% for those assets. Minification is a best practice that reduces download sizes without affecting functionality.
The site is served through a Content Delivery Network (CDN), which caches static assets at edge servers around the world. This means visitors from different geographic regions receive content from the nearest edge server, significantly reducing latency. CDN usage is particularly important for websites with a global audience, as it can reduce page load times by 40-60% for distant visitors.
From an environmental perspective, each page view of myworkpay.com produces approximately 0.06g of CO₂, earning a carbon rating of A. This places the website among the cleanest on the web, demonstrating efficient use of server resources and optimized content delivery. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 125 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for myworkpay.com. This typically means the site doesn't have enough real-world Chrome user traffic to generate statistically significant field data, or the domain is not included in the CrUX dataset. Core Web Vitals (LCP, INP, CLS) are important Google ranking factors that measure real user experience.
Core Web Vitals data not available
Requires CrUX API key configuration
Carbon Footprint
CO₂ per page view0.06g
RatingA
Page Weight & Optimization
HTML Size125 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Total Requests370
3rd Party Domains26
CSS Minified1/4
JS Minified1/18
myworkpay.com DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
myworkpay.com resolves to the IPv4 address 198.202.211.1, but does not support IPv6. IPv6 adoption is increasingly important as IPv4 address space becomes exhausted, and some ISPs and regions are transitioning to IPv6-only connectivity. The domain has 1 A record(s) configured.
The domain name system is managed by 2 name servers: justin.ns.cloudflare.com and sandy.ns.cloudflare.com. Having 2 name servers provides good redundancy — if one fails, the others can continue serving DNS queries. The choice of name servers often indicates the DNS hosting provider or CDN service being used.
Email for myworkpay.com is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 more. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server.
SPF (Sender Policy Framework) is configured, which specifies which mail servers are authorized to send email on behalf of this domain. This helps prevent email spoofing and improves email deliverability. DMARC (Domain-based Message Authentication, Reporting and Conformance) is configured with a reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit.
DNSSEC is not enabled for myworkpay.com. While not critical for most websites, DNSSEC adds an important security layer by ensuring DNS responses haven't been tampered with during transit. Enabling DNSSEC is recommended for domains handling sensitive data or financial transactions.
Our subdomain enumeration scan discovered 8 active subdomains for myworkpay.com: admin.myworkpay.com, api.myworkpay.com, app.myworkpay.com, mail.myworkpay.com, smtp.myworkpay.com, staging.myworkpay.com, webmail.myworkpay.com, and www.myworkpay.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
NS
justin.ns.cloudflare.com
sandy.ns.cloudflare.com
MX
aspmx.l.google.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
alt3.aspmx.l.google.com
alt4.aspmx.l.google.com
Email & Authentication
MX ProviderGoogle Workspace
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (8 found)
admin.myworkpay.com api.myworkpay.com app.myworkpay.com mail.myworkpay.com smtp.myworkpay.com staging.myworkpay.com webmail.myworkpay.com www.myworkpay.com
myworkpay.com Page Content, Images & Accessibility
🤖 AI Summary
The homepage of myworkpay.com contains 2,083 words of visible text content. This is a substantial amount of content that provides good opportunities for search engine indexing. The page is structured with 13 H2 headings, 18 H3 headings, 4 H4 headings, 3 H5, and 0 H6 headings.
The page includes 155 images. 60 images (39%) are missing alt text attributes, which is a significant concern for both accessibility and SEO. Screen readers rely on alt text to describe images to visually impaired users, and search engines use alt text to understand image content. Only 61% of images have proper alt text — we recommend adding descriptive alt attributes to all images.
The link structure consists of 156 internal links pointing to other pages on the same domain and 21 external links pointing to third-party websites. The high number of internal links suggests a well-interconnected site structure, which helps search engines discover and crawl all pages efficiently. There are 18 external JavaScript files, 4 CSS stylesheets, and 1 iframes on the page.
The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages) and robots.txt (controls search engine crawling behavior).
Notable missing features: Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.
We detected the following payment methods accepted on myworkpay.com: Visa and Discover. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.
The website has social media presence across 4 platforms: Facebook (@workpayhq), Twitter (@uwt.js), Instagram (@workpayhq), and Linkedin (@workpayafrica). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
Content Structure
H1Workpay: HR & Payroll Management Software for
H2 Tags13
H3 Tags18
H4 Tags4
H5 Tags3
H6 Tags0
Internal Links156
External Links21
Assets & Features
JavaScript Files18
JS Minified1/18
CSS Files4
CSS Minified1/4
Iframes1
Images155
Missing Alt60
SitemapYes ✓
Robots.txtYes ✓
PWANo
AMPNo
RSS FeedNo
Payment Methods Detected
Social Media Presence
Facebook: @workpayhqTwitter: @uwt.jsInstagram: @workpayhqLinkedin: @workpayafrica
myworkpay.com SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for myworkpay.com is well-optimized at 52 characters: "Global EOR and Payroll Software Solutions for Africa". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation.
The meta description is 155 characters (well-optimized): ""Looking to hire globally? Our Employer of Record (EOR) and payroll solution makes it easy to employ and pay teams acros...". Google typically displays up to 155-160 characters of the meta description in search results. A compelling meta description with a clear call-to-action can significantly improve click-through rates from search results.
The canonical url is correctly set to https://www.myworkpay.com, preventing duplicate content issues, the page language is declared as en, and a favicon is configured.
Open Graph meta tags are configured with 3/4 recommended fields: OG title ("Global EOR and Payroll Software Solutions for Africa..."), OG description, OG type (website). These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol.
A Twitter Card of type summary_large_image is configured, which controls how links appear when shared on Twitter/X. The "summary_large_image" type displays a large image preview, which typically generates higher engagement rates than the basic card type.
Google SERP Preview
Global EOR and Payroll Software Solutions for Africa
https://myworkpay.com
"Looking to hire globally? Our Employer of Record (EOR) and payroll solution makes it easy to employ and pay teams across Africa and the world compliantly.
Meta Tags
TitleGlobal EOR and Payroll Software Solutions for Africa...
Title Length52 chars
Meta Desc Length155 chars
H1Workpay: HR & Payroll Management Software for
Languageen
Canonicalhttps://www.myworkpay.com
Meta Robotsnot set
Meta Keywordsnot set
Schema.org & Social
Schema Types—
OG Typewebsite
OG ImageNot set
Twitter Cardsummary_large_image
FaviconSet ✓
myworkpay.com Related Domains & Cross-References
🤖 AI Summary
Related domain discovery works by finding other websites that share the same IP address, Google Tag Manager container ID, Google Analytics property, or advertising pixel IDs with myworkpay.com. This data becomes available after batch-crawling the domain database — individual domain lookups cannot populate this section. We extracted the following tracking IDs that can be used for cross-referencing: gtm_id: GTM-NTLVQPZ, hotjar_id: 3469042, intercom_app_id: jjzx1va4.
Tracking IDs for Cross-Referencing
gtm_idGTM-NTLVQPZ
hotjar_id3469042
intercom_app_idjjzx1va4
Related Domains
Related domain data requires database (populated after batch crawl)