webpush.jp

We performed a comprehensive analysis of webpush.jp on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 13179ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 40 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by GlobalSign nv-sa (OV type). The connection is encrypted using TLS 1.2 with the ECDHE-RSA-AES128-GCM-SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2027-01-03, which is 188 days from now. The security headers analysis reveals a score of 0/100 (poor). No security headers are configured, which is a significant security concern. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, 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 4 technologies across 4 categories powering webpush.jp. The detected stack includes Next.js chunks, React, Google Tag Manager, and Font Awesome. The site uses Next.js as its primary framework (version chunks). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, webpush.jp receives an overall trust score of 63/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, webpush.jp receives a trust score of 63/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, a valid SSL certificate issued by GlobalSign nv-sa with 188 days until expiration, and SPF (Sender Policy Framework) email authentication preventing email spoofing. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), 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 webpush.jp 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.

Our technology detection engine scanned webpush.jp 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. Framework: Next.js (version chunks) — provides the application framework and routing for webpush.jp. UI Library: React — handles the user interface rendering and component management for webpush.jp. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for webpush.jp. Icon Set: Font Awesome — provides additional functionality for webpush.jp. We also extracted the following tracking identifiers: Google Tag Manager container GTM-MTTVH4V. These IDs can be used to identify other websites operated by the same organization.

webpush.jp delivers its homepage in 13179ms (server response time), which is considered slow by industry standards. The total page weight is 40 KB, and we detected 174 resource requests loading assets from 7 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 5 CSS files and 0 out of 11 JavaScript files are minified. Minifying the remaining 16 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. From an environmental perspective, each page view of webpush.jp produces approximately 0.02g 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 40 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for webpush.jp. 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.

webpush.jp resolves to the IPv4 address 166.117.47.78, 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: ns1.value-domain.com and ns2.value-domain.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 webpush.jp 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 is not configured, leaving the domain vulnerable to email spoofing and phishing attacks that impersonate this domain. 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 webpush.jp. 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 homepage of webpush.jp contains 157 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 4 H2 headings, 11 H3 headings, 3 H4 headings. The page includes 84 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 20 internal links pointing to other pages on the same domain and 6 external links pointing to third-party websites. There are 11 external JavaScript files, 5 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 Progressive Web App (PWA) manifest (enabling app-like installation). Notable missing features: robots.txt and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 1 platforms: Facebook (@share.php). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for webpush.jp is well-optimized at 31 characters: "PUSH ONEのWEBプッシュ通知で能動的なマーケティングを". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 112 characters (well-optimized): "WEBサイト（ブラウザ）のプッシュ通知で効果的なマーケティングを実現できる「PUSH ONE」。サイトの認知率、カート落ち・フォーム落ちによるCV改善を実現します。WEBプッシュ通知なら株式会社シグニティのPUSH ONE。". 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 page language is declared as ja and a favicon is configured. No Open Graph tags are configured. When someone shares a link to webpush.jp 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 meta keywords tag contains 5 terms including シグニティ, プッシュ通知, プッシュワン, PUSH ONE, and WebPush. 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.