1881.no Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of 1881.no on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 33918ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 58 KB.
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 3 technologies across 3 categories powering 1881.no. The detected stack includes Google Analytics 4, Google Tag Manager, and jQuery.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, 1881.no receives an overall trust score of 65/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time33918ms
ProtocolHTTP/2
Page Size58 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
ServerMicrosoft-IIS/10.0
Total Requests100
3rd Party Domains22
Redirect1 hop(s)
Detected Technologies (3)
📊 Google Analytics 4
🏷️ Google Tag Manager
📦 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
IssuerGoDaddy.com, Inc.
Issuer FullcountryName=US, stateOrProvinceName=Arizona, localityName=Scottsdale, organizationName=GoDaddy.com, Inc., organizationalUnitName=http://certs.godaddy.com/repository/, commonName=Go Daddy Secure Certificate Authority - G2
SubjectcommonName=*.1881.no
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
1881.no Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, 1881.no 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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, DKIM (DomainKeys Identified Mail) providing cryptographic email verification, and DNSSEC providing authenticated DNS responses.
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, and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved.
We checked 1881.no 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.
Trust Signals
✅ Valid HTTPS
✅ SPF configured
✅ DMARC configured (p=reject)
✅ DKIM configured
✅ DNSSEC enabled
⚠️ 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
1881.no Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned 1881.no 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 1881.no.
Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for 1881.no.
JavaScript Library: jQuery — provides utility functions and DOM manipulation for 1881.no.
We also extracted the following tracking identifiers: Google Tag Manager container GTM-WD5JGQ. These IDs can be used to identify other websites operated by the same organization.
Analytics
📊 Google Analytics 4(95%)
Tag Manager
🏷️ Google Tag Manager(95%)
JavaScript Library
Tracking IDs
1881.no Performance, Speed & Core Web Vitals
🤖 AI Summary
1881.no delivers its homepage in 33918ms (server response time), which is considered slow by industry standards. The total page weight is 58 KB, and we detected 100 resource requests loading assets from 22 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 2 CSS files and 1 out of 6 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.
From an environmental perspective, each page view of 1881.no produces approximately 0.03g 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 58 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for 1881.no. 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.03g
RatingA
Page Weight & Optimization
HTML Size58 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
Total Requests100
3rd Party Domains22
CSS Minified0/2
JS Minified1/6
1881.no DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
1881.no resolves to the IPv4 address 20.100.178.65, 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 3 name servers: ns1.hyp.net, ns2.hyp.net, and ns3.hyp.net. Having 3 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 1881.no is handled by Microsoft 365 with 1 MX records configured: 1881-no.mail.protection.outlook.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 enabled for 1881.no, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites.
Our subdomain enumeration scan discovered 3 active subdomains for 1881.no: api.1881.no, mail.1881.no, and www.1881.no. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
NS
ns1.hyp.net
ns2.hyp.net
ns3.hyp.net
MX
1881-no.mail.protection.outlook.com
Email & Authentication
MX ProviderMicrosoft 365
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (3 found)
api.1881.no mail.1881.no www.1881.no
1881.no Page Content, Images & Accessibility
🤖 AI Summary
The homepage of 1881.no contains 240 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 14 H2 headings, 0 H3 headings, 0 H4 headings.
The page includes 7 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 10 internal links pointing to other pages on the same domain and 64 external links pointing to third-party websites. There are 6 external JavaScript files, 2 CSS stylesheets, and 1 iframes on the page.
The site implements the following web standards and features: Schema.org structured data (ContactPoint, EntryPoint, Organization, SearchAction, and WebSite) and Progressive Web App (PWA) manifest (enabling app-like installation).
Notable missing features: XML Sitemap and robots.txt. Adding these could improve search engine discoverability and rich result eligibility.
The website has social media presence across 3 platforms: Facebook (@1881.no), Linkedin (@digitale-medier-1881-as), and Youtube (@UC5kZCHffivOX48x8mOWJxkQ). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
Content Structure
H1—
H2 Tags14
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links10
External Links64
Assets & Features
JavaScript Files6
JS Minified1/6
CSS Files2
CSS Minified0/2
Iframes1
Images7
Missing Alt0
SitemapNo
Robots.txtNo
PWAYes ✓
AMPNo
RSS FeedNo
Schema.org Types
ContactPointEntryPointOrganizationSearchActionWebSite
Social Media Presence
Facebook: @1881.noLinkedin: @digitale-medier-1881-asYoutube: @UC5kZCHffivOX48x8mOWJxkQ
1881.no SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for 1881.no is well-optimized at 57 characters: "Opplysningen 1881® - telefonkatalogen og nummeropplysning". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation.
The meta description is 155 characters (well-optimized): "Opplysningen 1881® gir deg Norges mest oppdaterte telefonkatalog. Søk etter pålitelig nummeropplysning på personer og be...". 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 no, the meta robots directive is set to index,follow, and a favicon is configured.
Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Opplysningen 1881, telefonkatalogen, kart, tlf, nummeropplys..."), OG description, OG image (social sharing thumbnail), 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.
The site implements Schema.org structured data with the following types: ContactPoint, EntryPoint, Organization, SearchAction, 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
Opplysningen 1881® - telefonkatalogen og nummeropplysning
https://1881.no
Opplysningen 1881® gir deg Norges mest oppdaterte telefonkatalog. Søk etter pålitelig nummeropplysning på personer og bedrifter. Finn det du trenger raskt!
Meta Tags
TitleOpplysningen 1881® - telefonkatalogen og nummeropplysning...
Title Length57 chars
Meta Desc Length155 chars
H1—
Languageno
Canonical—
Meta Robotsindex,follow
Meta Keywordsnot set
Schema.org & Social
Schema TypesContactPoint, EntryPoint, Organization, SearchAction, WebSite
OG Typewebsite
OG ImageSet ✓
Twitter Card—
FaviconSet ✓
Open Graph Preview
1881.no
Opplysningen 1881, telefonkatalogen, kart, tlf, nummeropplysning, telefonnummer
Opplysningen 1881. Telefonkatalogen for bedrifter og personer samt kart