Skip to content
https://here.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.here.com/
200https://here.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://here.com/ → https://www.here.com:443/

Consistent

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

Certificate validity

124
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, 83 ms lookup
PASS
2 A records, 83 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 76.223.8.8, 13.248.132.24
Info::
No IPv6 (AAAA) records
Info::
12 nameserver(s) configured
Got: a22-65.akam.net, a1-19.akam.net, dns2.p09.nsone.net, a26-64.akam.net, a7-65.akam.net, a12-67.akam.net, ns1.heredns.com, dns1.p09.nsone.net, dns4.p09.nsone.net, dns3.p09.nsone.net, ns2.heredns.com, a3-67.akam.net
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: 83 ms
Got: 83 ms
A76.223.8.8, 13.248.132.24
AAAA—
CNAME—
NSa22-65.akam.net, a1-19.akam.net, dns2.p09.nsone.net, a26-64.akam.net, a7-65.akam.net, a12-67.akam.net, ns1.heredns.com, dns1.p09.nsone.net, dns4.p09.nsone.net, dns3.p09.nsone.net, ns2.heredns.com, a3-67.akam.net
MX
10 here-com.mail.protection.outlook.com
TXT
atlassian-domain-verification=knF3haFOOasaERvDLZ795cGspEEaz499y1dgADYbJfxONd95LV...
google-site-verification=eVEphaBV3aY_jTy1IujBOWAD4D9VggNTpX300JU25gE
00d3000000002omeaq
adobe-idp-site-verification=ca61d106e0ad3cb38bc6258c8007e36dd2c3d9baea6ce421e8bd...
google-gws-recovery-domain-verification=66630764
google-site-verification=ovpTI1YuPdCpurXmNDz2eGlHY34CnRd3ftsLfRFk-c0
perplexity-ai-domain-verification-9ax2p6=Pblyo18NPFFDHyXpDSOTebuoS
1b0f8b7e3fbaf34f9a9ffcf267508867312e1e56
canva-site-verification=Eg27_3yfFZpMtCzlFVp2wA
anthropic-domain-verification-tktsqv=S8QyBonaZHMWXBiFPpVJcck73
atlassian-sending-domain-verification=f892bdc4-8d01-4515-9e95-3db2a1018109
logmein-verification-code=062d72cf-3a8e-4578-86b0-452a2f20001d
apple-domain-verification=IydNaiRpdDd67o0r
SPF v=spf1 exists:%{i}._i.%{d}._d.espf.agari-dns.net include:%{d}.78.spf-protect.aga...
_globalsign-domain-verification=9tlf4hEXlOaZqOFoowID-tBkfjgVsssho2br9vuOxR
docker-verification=6366f93c-684d-44d8-a76a-97971d130740
6c944492-d556-4554-bd7e-1b2ff51ca59a
docusign=3a0d9103-d6cc-4cd7-bfbf-aee4ec88a966
have-i-been-pwned-verification=dweb_3zebzhyptns2mtyxjcrwq3n0
asv=1481dffe886a8f6537847ca57a22160a
atlassian-sending-domain-verification=a8b87eb2-63b0-4836-b8c2-0f4e32405904
dropbox-domain-verification=txb9fya2axdg
Sendinblue-code:dfdedce690b4d15768bae4d243d89107
cisco-ci-domain-verification=33c6123c3592ec326c4b0d681446794d9538f89253d951f8011...
google-gws-recovery-domain-verification=67087515
mandrill_verify.qN3HESgHxHApLmv1f9Okaw
2223ae76-c9dc-4163-9307-b8ee155dfdfe
google-site-verification=YPaVk3lUI0ka6AK1GyOOpbFVvxgYqB-5WDjmoT1JPro
uber-domain-verification=40f5bec1-6912-4f40-a0fb-649c0e4a364e
lovable_verification=2wFA6olft03eS3c9ZN8y
k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDQfJZX+lhjSK8lWu1hPKLI19UjJHpseso2...
CAALookup not available with standard resolver
Resolved in 83 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), 623 ms total
PASS
1 redirect(s), 623 ms total
Info::
Single redirect
Got: https://here.com → https://www.here.com:443/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 623 ms total
Got: 623 ms

https://here.com

405 ms · HTTP/1.1

301

https://www.here.com:443/

218 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://here.com301405 msHTTP/1.1awselb/2.0
2https://www.here.com:443/200218 msHTTP/1.1Vercel

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 4105 URLs
PASS
robots.txt present, sitemap with 4105 URLs
Info::
robots.txt is present
Got: 1734 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4105 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1734 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Disallow NextJs paths
Disallow: /_next/
Disallow: /api/
Disallow: /admin/
Disallow: /private/
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips/
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register/
Disallow: /user/password/
Disallow: /user/login/
Disallow: /user/logout/
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips/
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password/
Disallow: /index.php/user/register/
Disallow: /index.php/user/login/
Disallow: /index.php/user/logout/

Sitemap: https://www.here.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 4105 entries Valid XML Yes
Sample URLs:
A
Domain Intelligence
here.com — via MarkMonitor Inc., 31 years, 3 months old, hosted on AWS
PASS
here.com — via MarkMonitor Inc., 31 years, 3 months old, hosted on AWS
Warning::
Domain expires in 48 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 10, 2026
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: MarkMonitor 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

EXPIRED

June 10, 2026

SSL certificate

124 days

Issued by GlobalSign nv-sa

Domain age

31 years, 3 months

Registered June 11, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

76.223.8.8

Registrar

MarkMonitor Inc.

Unlocked 12 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created June 11, 1995 (31 years, 3 months ago)
Expires June 10, 2026 (1 months)
Last Updated May 9, 2025
Name Servers a1-19.akam.net, a12-67.akam.net, a22-65.akam.net, a26-64.akam.net, a3-67.akam.net, a7-65.akam.net, dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, ns1.heredns.com, ns2.heredns.com
DNSSEC Not enabled
Hosting
IP Address 76.223.8.8
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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 452 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
31 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
315 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
452 ms
Total Time Total request time from DNS lookup through full response.
452 ms

Connection waterfall

DNS Lookup 31 ms TCP Connect 1 ms TLS Handshake 315 ms Server Processing 105 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