Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNS Records8 A records, 44 ms lookupREVIEW
| A | 63.177.3.2, 3.64.83.125, 63.182.192.124, 35.157.118.183, 52.57.168.54, 18.197.59.255, 3.127.176.91, 18.196.117.152 |
| AAAA | — |
| CNAME | front-geo.production.opera-website.route53.opera.com |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations106 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+Redirect ChainNo redirects — direct accessPASS
https://www.opera.com
138 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.opera.com | 200 | 138 ms | HTTP/1.1 |
A+Crawlabilityrobots.txt present, sitemap with 2 URLsPASS
User-agent: *
Allow: /help/tutorials/
Allow: /browser/tutorials/
Allow: /support/tutorials/
Allow: /lp/students
Allow: /pt-br/lp/students
Allow: /lp/br-themes
Allow: /pt-br/lp/br-themes
Allow: /lp/video-streaming
Allow: /*/lp/video-streaming
Disallow: /o/
Disallow: /*/o/
Disallow: /abtest/
Disallow: /*/abtest/
Disallow: /api/
Disallow: /client/
Disallow: /downloadassets/
Disallow: /*/downloadassets/
Disallow: /download/get*
Disallow: /get$
Disallow: /get/
Disallow: /promoassets/
Disallow: /*/promoassets/
Disallow: /campaign/
Disallow: /*/campaign/
Disallow: /suite/
Disallow: /*/suite/
Disallow: /info/
Disallow: /*/info/
Disallow: /computer/thanks
Disallow: /*/computer/thanks
Disallow: /computer/thanks-partner
Disallow: /*/computer/thanks-partner
Disallow: /ofa/
Disallow: /*/ofa/
Disallow: /oma/
Disallow: /*/oma/
Disallow: */tlp/*
Disallow: */lp/*
Disallow: /tutorials
Disallow: /*/tutorials
Disallow: /opera/features
Disallow: /*/opera/features
Disallow: /opera-coupons-uninstall
Sitemap: https://www.opera.com/sitemap-index.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligenceopera.com — via NameWeb BVBA, 27 years, 4 months old, hosted on NO-OPERA, NOPASS
240 days
April 14, 2027
106 days
Issued by Trust Provider B.V.
27 years, 4 months
Registered April 14, 1999
Not enabled
Protects against DNS spoofing
NO-OPERA, NO
ASN AS39832
185.26.182.104
NameWeb BVBA
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033