168.am

🤖 AI Summary

After conducting a thorough safety and legitimacy analysis, 168.am receives a trust score of 65/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, 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 168.am 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.

🤖 AI Summary

Our technology detection engine scanned 168.am and identified 10 distinct technologies across 8 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CMS: WordPress (version 6.9.4) — manages the content and page structure for 168.am. CSS Framework: Bootstrap (version 4.3.1) — provides the styling and responsive layout system for 168.am. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for 168.am. Advertising: Meta Pixel and Google AdSense — handles advertising pixel tracking and conversion measurement for 168.am. CDN: Cloudflare and StackPath — accelerates content delivery by caching assets at edge locations worldwide for 168.am. Video: YouTube Embed — provides video hosting and playback for 168.am. JavaScript Library: jQuery (version 3.3.1.) — provides utility functions and DOM manipulation for 168.am. Icon Set: Font Awesome — provides additional functionality for 168.am. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-VQBJ6YGDL7. These IDs can be used to identify other websites operated by the same organization.

🤖 AI Summary

168.am delivers its homepage in 18534ms (server response time), which is considered slow by industry standards. The total page weight is 259 KB, and we detected 654 resource requests loading assets from 14 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: 3 out of 5 CSS files and 4 out of 9 JavaScript files are minified. Minifying the remaining 7 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 168.am produces approximately 0.13g 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 259 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for 168.am. 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.

🤖 AI Summary

168.am resolves to the IPv4 address 172.67.70.99 and also supports IPv6 (2606:4700:20::ac43:4663), demonstrating modern network infrastructure readiness. The domain has 3 A record(s) configured. The domain name system is managed by 2 name servers: brad.ns.cloudflare.com and kami.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 168.am 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 168.am. 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 2 active subdomains for 168.am: blog.168.am and www.168.am. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

🤖 AI Summary

The homepage of 168.am contains 3,186 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 34 H2 headings, 0 H3 headings, 0 H4 headings, 1 H5, and 0 H6 headings. The page includes 177 images. 169 images (95%) 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 5% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 371 internal links pointing to other pages on the same domain and 10 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 9 external JavaScript files, 5 CSS stylesheets, and 4 iframes on the page. The site implements the following web standards and features: Progressive Web App (PWA) manifest (enabling app-like installation). Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on 168.am: 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 2 platforms: Facebook (@168.am) and Twitter (@168am_official). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

🤖 AI Summary

The title tag for 168.am is good at 69 characters: "Նորություններ հայաստանում | Norutyunner hayastanum | Lurer hayastanic". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 182 characters (slightly long): "168.am լրատվական կայքը «168 Ժամի» գործունեության շարունակությունն ու ընդլայնումն է վիրտուալ տարածության մեջ: Ամենաթարմ ե...". 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 meta robots directive is set to max-image-preview:large and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("Նորություններ հայաստանում | Norutyunner hayastanum | Lurer h..."), OG description, OG image (social sharing thumbnail), These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol.

🤖 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 168.am. 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: ga4_id: G-VQBJ6YGDL7.