Skip to content
https://globenewswire.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.globenewswire.com/
200https://globenewswire.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://globenewswire.com/ → http://www.globenewswire.com:80/

HTTP version does not redirect to HTTPS

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
TLS Certificate Expiry & Recommendations
257 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

257
days left
0d 30d 60d 90d+

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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+
DNS Records
2 A records, 36 ms lookup
PASS
2 A records, 36 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 98.87.210.157, 3.230.209.22
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-875.awsdns-45.net, ns-313.awsdns-39.com, ns-1384.awsdns-45.org, ns-2019.awsdns-60.co.uk
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 36 ms
Got: 36 ms
A98.87.210.157, 3.230.209.22
AAAA—
CNAME—
NSns-875.awsdns-45.net, ns-313.awsdns-39.com, ns-1384.awsdns-45.org, ns-2019.awsdns-60.co.uk
MX
1 notified-com.mail.protection.outlook.com
TXT
globalsign-domain-verification=UF-U5SZ5PkqwUWs29KoqaRpI2sGi5b3PAKN0QEq4Z7
MS=ms86576800
_globalsign-domain-verification=1WEo5KUX5wwxEpYMhRlfM3bG6w4SuqHHbTxBivLmBE
MS=ms61142723
_globalsign-domain-verification=A_raK5dpbXKx4NEIXrTcLSjZcDEFMap9EVEIkWOC-X
W0E0S41234
_globalsign-domain-verification=C8OI4CCQ-9b_tBGa6pzhjjzzGFmNOrwJPjjQJ-ROaZ
globalsign-domain-verification=A1CE40BD18D28DE3FD77688188789AA8
globalsign-domain-verification=de7230ff61b72e4d1033d8165f7cf002
SPF v=spf1 mx a include:amazonses.com include:spf.messagelabs.com include:spf.protec...
_globalsign-domain-verification=m3Dis1q8C1W1L29RAWii1JTUx_Eo54jZxXVEPpHaig
_globalsign-domain-verification=6U-t-VgCkKvru2jq-weczI5-bBRRUjDk7kNXzhkYon
globalsign-domain-verification=fa639e82da702c261b78e59649716641
google-site-verification=ZH9yMDKhIDp_c6FirZbhXObbQi7r-CamqdixJuIGcfo
CAALookup not available with standard resolver
Resolved in 36 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 606 ms total
PASS
1 redirect(s), 606 ms total
Info::
Single redirect
Got: https://globenewswire.com → https://www.globenewswire.com:443/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 606 ms total
Got: 606 ms

https://globenewswire.com

384 ms · HTTP/1.1

301

https://www.globenewswire.com:443/

221 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://globenewswire.com301384 msHTTP/1.1awselb/2.0
2https://www.globenewswire.com:443/200221 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 1000 URLs
PASS
robots.txt present, sitemap with 1000 URLs
Info::
robots.txt is present
Got: 1940 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1000 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1940 B Sitemaps referenced 7 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /SubscribeToRss/

Disallow: /News/Index

Disallow: /newsroom/rss/

Disallow: /newsroom/ctr

Disallow: /Tracker?data=*

Disallow: /api/

Disallow: /JsonData/

Disallow: /StockQuote/

Disallow: /en/StockQuote/

Disallow: /fr/StockQuote/

Disallow: /JSWidget/

Disallow: /en/JSWidget/

Disallow: /fr/JSWidget/

Disallow: /JSWidgetFeed/

Disallow: /en/JSWidgetFeed/

Disallow: /fr/JSWidgetFeed/

Disallow: /fr/Tracker?data=*

Disallow: /en/Tracker?data=*

Disallow: */news-release/*.html?pdf=1

Disallow: /NewsRoom/ReleaseNg/

Sitemap: https://globenewswire.com/NewsRoom/GoogleSitemap

Sitemap: https://sitemaps.globenewswire.com/news-en.xml

Sitemap: https://sitemaps.globenewswire.com/news-fr.xml

Sitemap: https://sitemaps.globenewswire.com/news-de.xml

Sitemap: https://sitemaps.globenewswire.com/topics-en.xml

Sitemap: https://sitemaps.globenewswire.com/services-en.xml

Sitemap: https://sitemaps.globenewswire.com/services-de.xml

Allow: /news-release/

Disallow: /ar/

Disallow: /bg/

Disallow: /cs/

Disallow: /da/

Disallow: /el/

Disallow: /es/

Disallow: /et/

Disallow: /fi/

Disallow: /he/

Disallow: /hi/

Disallow: /hu/

Disallow: /hy/

Disallow: /id/

Disallow: /is/

Disallow: /it/

Disallow: /ja/

Disallow: /ko/

Disallow: /lt/

Disallow: /lv/

Disallow: /ms/

Disallow: /nb/

Disallow: /nl/

Disallow: /nn/

Disallow: /no/

Disallow: /pl/

Disallow: /pt/

Disallow: /ro/

Disallow: /ru/

Disallow: /sk/

Disallow: /sl/

Disallow: /sv/

Disallow: /th/

Disallow: /tr/

Disallow: /vi/

Disallow: /zh-Hans/

Disallow: /zh-Hant/

Disallow: /Ne/SocialMediaActivity/LogJSWidgetLinkClick

Disallow: /Tr/SocialMediaActivity/LogJSWidgetLinkClick

Disallow: /fr/Ne/

Disallow: /fr/Tr/

Disallow: /fr/ca/

Disallow: /fr/js/

Disallow: /fr/ph/

Disallow: /fr/us/

Disallow: /fr/zi/

Disallow: /v1/SocialMediaActivity/

Disallow: /Home/404Page

Disallow: /fr/Home/404Page

Disallow: */no-referrer-when-downgrade
sitemap.xml 200 OK
Type URL Set URLs 1000 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
globenewswire.com — via Amazon Registrar, Inc., 18 years, 10 months old, hosted on AWS
PASS
globenewswire.com — via Amazon Registrar, Inc., 18 years, 10 months old, hosted on AWS
Info::
Domain registered until Sep 8, 2026 (4 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Amazon Registrar, Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

56 days

September 8, 2026

SSL certificate

257 days

Issued by Amazon

Domain age

18 years, 10 months

Registered September 8, 2007

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

3.230.209.22

Registrar

Amazon Registrar, Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Amazon Registrar, Inc.
Created September 8, 2007 (18 years, 10 months ago)
Expires September 8, 2026 (4 months)
Last Updated February 25, 2026
Name Servers ns-1384.awsdns-45.org, ns-2019.awsdns-60.co.uk, ns-313.awsdns-39.com, ns-875.awsdns-45.net
DNSSEC Not enabled
Hosting
IP Address 3.230.209.22
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A
HTTP Probe Timing
Total 419 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
33 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
96 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
194 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
419 ms
Total Time Total request time from DNS lookup through full response.
420 ms

Connection waterfall

DNS Lookup 33 ms TCP Connect 96 ms TLS Handshake 194 ms Server Processing 96 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback