guardian.ng

HTTPS HTTP/2 Gzip Cloudflare WordPress Crawled in 58,851ms · June 27, 2026 20:14 UTC

guardian.ng Website Overview & Technology Report

🤖 AI Summary
We performed a comprehensive analysis of guardian.ng on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 717ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 788 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 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 7 technologies across 7 categories powering guardian.ng. The detected stack includes WordPress 6.7.2, Bootstrap, Google Analytics 4, Google AdSense, Cloudflare, Google Fonts, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, guardian.ng receives an overall trust score of 61/100, classified as "Likely Safe".
61
/ 100
Trust Score
0
/ 100
Security Headers
HTTP Response
Status200 OK
Response Time717ms
ProtocolHTTP/2
Page Size788 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Servercloudflare
Total Requests572
3rd Party Domains19
RedirectNone
Detected Technologies (7)
• WordPress 🎨 Bootstrap 📊 Google Analytics 4 📢 Google AdSense ☁️ Cloudflare 🔤 Google Fonts 📦 jQuery
Security Headers
Content-Security-Policy
Not set
Strict-Transport-Security (HSTS)
Not set
X-Frame-Options
Not 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=guardian.ng
Type
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm
Issued
Expires— (? days)
SANs

guardian.ng Trust Score & Safety Analysis

🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, guardian.ng receives a trust score of 61/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification. 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 guardian.ng 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.
61
/ 100
Likely Safe
Trust Signals
Valid HTTPS
SPF configured
DMARC configured (p=none)
DKIM configured
⚠️ DNSSEC not enabled
Sitemap.xml found
Robots.txt found
⚠️ Missing Content-Security-Policy
⚠️ Missing X-Frame-Options
⚠️ 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

guardian.ng Technology Stack & Detected Technologies

🤖 AI Summary
Our technology detection engine scanned guardian.ng and identified 7 distinct technologies across 7 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.7.2) — manages the content and page structure for guardian.ng. CSS Framework: Bootstrap — provides the styling and responsive layout system for guardian.ng. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for guardian.ng. Advertising: Google AdSense — handles advertising pixel tracking and conversion measurement for guardian.ng. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for guardian.ng. Fonts: Google Fonts — delivers web fonts for typography for guardian.ng. JavaScript Library: jQuery — provides utility functions and DOM manipulation for guardian.ng. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-20260626. These IDs can be used to identify other websites operated by the same organization.
CMS
• WordPress 6.7.2(100%)
CSS Framework
🎨 Bootstrap(95%)
Analytics
📊 Google Analytics 4(95%)
Advertising
📢 Google AdSense(95%)
CDN
☁️ Cloudflare(100%)
Fonts
🔤 Google Fonts(95%)
JavaScript Library
📦 jQuery(95%)
Tracking IDs
ga4_idG-20260626

guardian.ng Performance, Speed & Core Web Vitals

🤖 AI Summary
guardian.ng delivers its homepage in 717ms (server response time), which is considered average by industry standards. The total page weight is 788 KB, and we detected 572 resource requests loading assets from 19 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: 2 out of 5 CSS files and 5 out of 10 JavaScript files are minified. Minifying the remaining 8 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 guardian.ng produces approximately 0.38g of CO₂, earning a carbon rating of C. This is an average carbon footprint. Optimizing images and reducing unnecessary scripts could further improve this score. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 788 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for guardian.ng. 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.38g
RatingC
Page Weight & Optimization
HTML Size788 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Total Requests572
3rd Party Domains19
CSS Minified2/5
JS Minified5/10

guardian.ng DNS Records, Email Authentication & Domain Registration

🤖 AI Summary
guardian.ng resolves to the IPv4 address 104.26.4.228 and also supports IPv6 (2606:4700:20::681a:4e4), demonstrating modern network infrastructure readiness. The domain has 3 A record(s) configured. The domain name system is managed by 2 name servers: kianchau.ns.cloudflare.com and ophelia.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 guardian.ng is handled by guadian.ng with 2 MX records configured: email.guadian.ng and mail.guardian.ng. 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 none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. 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 guardian.ng. 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 4 active subdomains for guardian.ng: cdn.guardian.ng, mail.guardian.ng, status.guardian.ng, and www.guardian.ng. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
104.26.4.228
104.26.5.228
172.67.73.120
AAAA
2606:4700:20::681a:4e4
NS
kianchau.ns.cloudflare.com
ophelia.ns.cloudflare.com
MX
email.guadian.ng
mail.guardian.ng
Email & Authentication
SPF
DMARC p=none
DKIM
DNSSEC
MX Providerguadian.ng
Registrar
Organisation
Country
Contact
Registered
Expires
Domain Age
IPv6 SupportYes ✓
Subdomains (4 found)
cdn.guardian.ng mail.guardian.ng status.guardian.ng www.guardian.ng

guardian.ng Page Content, Images & Accessibility

🤖 AI Summary
The homepage of guardian.ng contains 2,338 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 124 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 76 images. 4 images (5%) 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 95% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 348 internal links pointing to other pages on the same domain and 43 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 10 external JavaScript files, 5 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), robots.txt (controls search engine crawling behavior), and Schema.org structured data (BreadcrumbList, EntryPoint, ImageObject, ListItem, Organization, PropertyValueSpecification, ReadAction, SearchAction, WebPage, and WebSite). The website has social media presence across 5 platforms: Facebook (@guardianng), Twitter (@GuardianNigeria), Instagram (@guardiannigeria), Linkedin (@guardian-newspapers-limited), and Github (@twbs). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
2,338
Words
76
Images
95%
Alt Text Score
788
Page Size (KB)
Content Structure
H1Nwankwo Kanu: A legacy from the archives
H2 Tags124
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links348
External Links43
Assets & Features
JavaScript Files10
JS Minified5/10
CSS Files5
CSS Minified2/5
Iframes0
Images76
Missing Alt4
SitemapYes ✓
Robots.txtYes ✓
PWANo
AMPNo
RSS FeedNo
Schema.org Types
BreadcrumbListEntryPointImageObjectListItemOrganizationPropertyValueSpecificationReadActionSearchActionWebPageWebSite
Social Media Presence
Facebook: @guardianngTwitter: @GuardianNigeriaInstagram: @guardiannigeriaLinkedin: @guardian-newspapers-limitedGithub: @twbs

guardian.ng SEO Analysis, Meta Tags & Open Graph

🤖 AI Summary
The title tag for guardian.ng is good at 61 characters: "Homepage | The Guardian Nigeria News - Nigeria and World News". The length is acceptable, though it may be slightly truncated in some search result displays. No meta description is configured for guardian.ng. 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://guardian.ng/, preventing duplicate content issues, the page language is declared as en-gb, the meta robots directive is set to index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1, and a favicon is configured. Open Graph meta tags are configured with 2/4 recommended fields: OG title ("Homepage..."), 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. The site implements Schema.org structured data with the following types: BreadcrumbList, EntryPoint, ImageObject, ListItem, Organization, PropertyValueSpecification, ReadAction, SearchAction, WebPage, and WebSite. 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.
Google SERP Preview
Homepage | The Guardian Nigeria News - Nigeria and World News
https://guardian.ng
Meta Tags
TitleHomepage | The Guardian Nigeria News - Nigeria and World New...
Title Length61 chars
Meta Desc Length0 chars
H1Nwankwo Kanu: A legacy from the archives
Languageen-GB
Canonicalhttps://guardian.ng/
Meta Robotsindex, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Meta Keywordsnot set
Schema.org & Social
Schema TypesBreadcrumbList, EntryPoint, ImageObject, ListItem, Organization, PropertyValueSpecification, ReadAction, SearchAction, WebPage, WebSite
OG Typewebsite
OG ImageNot set
Twitter Cardsummary_large_image
FaviconSet ✓