disabledperson.com

We performed a comprehensive analysis of disabledperson.com on 2026-07-01. The website returned an HTTP 200 status code with a server response time of 11117ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 74 KB, and the site is served behind a CDN (Content Delivery Network). The website uses a secure HTTPS connection with a valid SSL certificate issued by Amazon (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-09-06, which is 67 days from now. The security headers analysis reveals a score of 65/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. However, the site is missing Content-Security-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 3 technologies across 3 categories powering disabledperson.com. The detected stack includes Google Analytics 4, Google Tag Manager, and Stripe. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, disabledperson.com receives an overall trust score of 82/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, disabledperson.com receives a trust score of 82/100, which places it in the "Very 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, a valid SSL certificate issued by Amazon with 67 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, and a well-established domain registered for over 27.0 years, indicating long-term commitment and legitimacy. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, 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 disabledperson.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. The domain is registered through eNom, LLC based in IE, with a registration date of 1999-07-24 and expiration date of 2028-07-24.

Our technology detection engine scanned disabledperson.com and identified 3 distinct technologies across 3 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for disabledperson.com. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for disabledperson.com. Payments: Stripe — processes payment transactions for disabledperson.com. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-NTX5YBN3ZB and Google Tag Manager container GTM-TH8VP5K. These IDs can be used to identify other websites operated by the same organization.

disabledperson.com delivers its homepage in 11117ms (server response time), which is considered slow by industry standards. The total page weight is 74 KB, and we detected 207 resource requests loading assets from 4 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 1 CSS files and 0 out of 3 JavaScript files are minified. Minifying the remaining 4 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 disabledperson.com produces approximately 0.04g 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 74 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for disabledperson.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.

disabledperson.com resolves to the IPv4 address 18.165.122.75, 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 4 A record(s) configured. The domain name system is managed by 4 name servers: ns-1007.awsdns-61.net, ns-1372.awsdns-43.org, ns-1875.awsdns-42.co.uk, and ns-49.awsdns-06.com. 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 disabledperson.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 was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is not enabled for disabledperson.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. The domain is registered through eNom, LLC (IE). It was first registered on 1999-07-24 and is set to expire on 2028-07-24, making it 27.0 years old. Our subdomain enumeration scan discovered 2 active subdomains for disabledperson.com: mail.disabledperson.com and www.disabledperson.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of disabledperson.com contains 1,377 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 7 H2 headings, 3 H3 headings, 1 H4 headings, 6 H5, and 13 H6 headings. The page includes 6 images. 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 193 internal links pointing to other pages on the same domain and 2 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 3 external JavaScript files, 1 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior) and Schema.org structured data (ContactPoint and Organization). Notable missing features: XML Sitemap. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on disabledperson.com: Discover and Affirm. 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 3 platforms: Facebook (@disABLEDpersonInc), Twitter (@disabledjobs), and Linkedin (@disabledperson-inc.). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for disabledperson.com is too long at 101 characters: "Jobs for People with Disabilities | Find Inclusive Employment | DisabledPerson.c...". At 101 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning. The meta description is 166 characters (slightly long): "Discover accessible jobs for people with disabilities at DisabledPerson.com. Find inclusive employers committed to equal...". 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.disabledperson.com/, preventing duplicate content issues and the page language is declared as en. No Open Graph tags are configured. When someone shares a link to disabledperson.com on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing. The site implements Schema.org structured data with the following types: ContactPoint and Organization. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates. The meta keywords tag contains 4 terms including jobs for people with disabilities, disability employment, inclusive jobs, and accessible job. Note: Google has officially confirmed that it does not use the meta keywords tag as a ranking signal. However, some other search engines (Bing, Yandex) may still reference it.