mypci.com

HTTPS HTTP/2 HSTS Gzip Crawled in 79,149ms · June 28, 2026 00:39 UTC

mypci.com Website Overview & Technology Report

🤖 AI Summary
We performed a comprehensive analysis of mypci.com on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 16956ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 111 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 Referrer-Policy. However, the site is missing X-Frame-Options, X-Content-Type-Options, 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 4 technologies across 4 categories powering mypci.com. The detected stack includes React, HubSpot, reCAPTCHA v3, and Font Awesome. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, mypci.com receives an overall trust score of 72/100, classified as "Likely Safe".
72
/ 100
Trust Score
55
/ 100
Security Headers
HTTP Response
Status200 OK
Response Time16956ms
ProtocolHTTP/2
Page Size111 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Servercloudflare
Total Requests30
3rd Party Domains2
Redirect1 hop(s)
Detected Technologies (4)
⚛️ React 📣 HubSpot 🔒 reCAPTCHA v3 🎯 Font Awesome
Security Headers
Content-Security-Policy
Set ✓
Strict-Transport-Security (HSTS)
Set ✓
X-Frame-Options
Not set
X-Content-Type-Options
Not set
Referrer-Policy
Set ✓
Permissions-Policy
Not set
SSL Certificate
IssuerLet's Encrypt
Issuer FullcountryName=US, organizationName=Let's Encrypt, commonName=YE1
SubjectcommonName=8e4c6f8e.sni.cloudflaressl.com
Type
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm
Issued
Expires— (? days)
SANs

mypci.com Trust Score & Safety Analysis

🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, mypci.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: no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), 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 mypci.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.
72
/ 100
Likely Safe
Trust Signals
Valid HTTPS
HSTS enabled
SPF configured
DMARC configured (p=reject)
DKIM configured
⚠️ DNSSEC not enabled
Sitemap.xml found
Robots.txt found
⚠️ Missing X-Frame-Options
Blacklist Checks (8/8 clean)
Google Safe Browsing clean
Phishtank clean
Urlhaus clean
Openphish clean
Dnsfilter clean
Spamhaus Dbl clean
Surbl clean
Virustotal clean

mypci.com Technology Stack & Detected Technologies

🤖 AI Summary
Our technology detection engine scanned mypci.com and identified 4 distinct technologies across 4 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. UI Library: React — handles the user interface rendering and component management for mypci.com. Marketing: HubSpot — provides marketing automation capabilities for mypci.com. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for mypci.com. Icon Set: Font Awesome — provides additional functionality for mypci.com.
UI Library
⚛️ React(95%)
Marketing
📣 HubSpot(95%)
Security
🔒 reCAPTCHA v3(95%)
Icon Set
🎯 Font Awesome(95%)

mypci.com Performance, Speed & Core Web Vitals

🤖 AI Summary
mypci.com delivers its homepage in 16956ms (server response time), which is considered slow by industry standards. The total page weight is 111 KB, and we detected 30 resource requests loading assets from 2 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: 0 out of 9 CSS files and 0 out of 5 JavaScript files are minified. Minifying the remaining 14 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 mypci.com produces approximately 0.05g 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 111 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for mypci.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.05g
RatingA
Page Weight & Optimization
HTML Size111 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Total Requests30
3rd Party Domains2
CSS Minified0/9
JS Minified0/5

mypci.com DNS Records, Email Authentication & Domain Registration

🤖 AI Summary
mypci.com resolves to the IPv4 address 199.60.103.4, 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 2 A record(s) configured. The domain name system is managed by 4 name servers: ns-1410.awsdns-48.org, ns-1716.awsdns-22.co.uk, ns-202.awsdns-25.com, and ns-659.awsdns-18.net. Having 4 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 mypci.com is handled by Google Workspace with 1 MX records configured: smtp.google.com. 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 mypci.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 1 active subdomains for mypci.com: www.mypci.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
199.60.103.4
199.60.103.104
NS
ns-1410.awsdns-48.org
ns-1716.awsdns-22.co.uk
ns-202.awsdns-25.com
ns-659.awsdns-18.net
MX
smtp.google.com
Email & Authentication
SPF
DMARC p=reject
DKIM
DNSSEC
MX ProviderGoogle Workspace
Registrar
Organisation
Country
Contact
Registered
Expires
Domain Age
IPv6 SupportNo
Subdomains (1 found)
www.mypci.com

mypci.com Page Content, Images & Accessibility

🤖 AI Summary
The homepage of mypci.com contains 19 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 1 image. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content). The link structure consists of 2 internal links pointing to other pages on the same domain and 0 external links pointing to third-party websites. There are 5 external JavaScript files, 9 CSS stylesheets, and 0 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. The website has social media presence across 1 platforms: Github (@necolas). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
19
Words
1
Images
100%
Alt Text Score
111
Page Size (KB)
Content Structure
H1
H2 Tags0
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links2
External Links0
Assets & Features
JavaScript Files5
JS Minified0/5
CSS Files9
CSS Minified0/9
Iframes0
Images1
Missing Alt0
SitemapYes ✓
Robots.txtYes ✓
PWANo
AMPNo
RSS FeedNo
Social Media Presence
Github: @necolas

mypci.com SEO Analysis, Meta Tags & Open Graph

🤖 AI Summary
The title tag for mypci.com is good at 9 characters: "Mypci.com". The length is acceptable, though it may be slightly truncated in some search result displays. No meta description is configured for mypci.com. This is a critical SEO oversight — without a meta description, Google will auto-generate a snippet from page content, which may not accurately represent the page or entice users to click. Adding a unique, compelling meta description of 120-155 characters is strongly recommended. The canonical url is correctly set to https://www.mypci.com, preventing duplicate content issues, the page language is declared as en, and a favicon is configured. Open Graph meta tags are configured with 1/4 recommended fields: OG title ("Mypci.com..."), 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 is configured, which controls how links appear when shared on Twitter/X. The "summary" type displays a large image preview, which typically generates higher engagement rates than the basic card type.
Google SERP Preview
Mypci.com
https://mypci.com
Meta Tags
TitleMypci.com...
Title Length9 chars
Meta Desc Length0 chars
H1
Languageen
Canonicalhttps://www.mypci.com
Meta Robotsnot set
Meta Keywordsnot set
Schema.org & Social
Schema Types
OG Type
OG ImageNot set
Twitter Cardsummary
FaviconSet ✓