Skip to content
https://meraki.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
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

C
Crawlability
Action
robots.txt present, sitemap with 8 URLs
REVIEW
robots.txt present, sitemap with 8 URLs
Info::
robots.txt is present
Got: 2213 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8 entries
Info::
Sitemap index with 8 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 2213 B Sitemaps referenced 0 User-agents ichiro, Lycos, msnbot-media, Slurp, Sogou spider2, coccoc, Findxbot, Teoma, Yeti, Baiduspider, HaoSouSpider, msnbot, Plukkie, Sogou blog, wotbox, 360Spider-Image, 360Spider-Video, SeznamBot, DeuSu, DuckDuckBot, istellabot, Twitterbot, YoudaoBot, Googlebot, Googlebot-News, Mail.Ru, Baiduspider-news, Baiduspider-video, Googlebot-Mobile, SputnikBot, AdsBot-Google, Sogou News Spider, YandexMobileBot, *, AdsBot-Google-Mobile-Apps, Sogou inst spider, adidxbot, CCBot, Dazoobot, Mediapartners-Google, AdsBot-Google-Mobile, Cliqzbot, Rambler, Sogou web spider, Daumoa, yacybot, YioopBot, Baiduspider-image, Exploratodo, Facebot, OrangeBot, Pinterest, Googlebot-Image, MojeekBot, Qwantify, Sosospider, AppleNewsBot, coccocbot-web, DuckDuckGo-Favicons-Bot, JikeSpider, Sogou Orion spider, Yandex, yoozBot, 360Spider, Applebot, bingbot, BingPreview, BublupBot, coccocbot-image, EuripBot, Feedly, Googlebot-Video Blocking Yes — all crawlers blocked
################################# ROBOTS.TXT ###################################

# Updates can be retrieved from: https://github.com/jonasjacek/robots.txt      #

# This document is licensed with a CC BY-NC-SA 4.0 license.                    #

# Last update: 2020-02-20                                                      #

################################################################################

User-agent: 360Spider

User-agent: 360Spider-Image

User-agent: 360Spider-Video

User-agent: AdsBot-Google

User-agent: AdsBot-Google-Mobile

User-agent: AdsBot-Google-Mobile-Apps

User-agent: adidxbot

User-agent: Applebot

User-agent: AppleNewsBot

User-agent: Baiduspider

User-agent: Baiduspider-image

User-agent: Baiduspider-news

User-agent: Baiduspider-video

User-agent: bingbot

User-agent: BingPreview

User-agent: BublupBot

User-agent: CCBot

User-agent: Cliqzbot

User-agent: coccoc

User-agent: coccocbot-image

User-agent: coccocbot-web

User-agent: Daumoa

User-agent: Dazoobot

User-agent: DeuSu

User-agent: DuckDuckBot

User-agent: DuckDuckGo-Favicons-Bot

User-agent: EuripBot

User-agent: Exploratodo

User-agent: Facebot

User-agent: Feedly

User-agent: Findxbot

User-agent: Googlebot

User-agent: Googlebot-Image

User-agent: Googlebot-Mobile

User-agent: Googlebot-News

User-agent: Googlebot-Video

User-agent: HaoSouSpider

User-agent: ichiro

User-agent: istellabot

User-agent: JikeSpider

User-agent: Lycos

User-agent: Mail.Ru

User-agent: Mediapartners-Google

User-agent: MojeekBot

User-agent: msnbot

User-agent: msnbot-media

User-agent: OrangeBot

User-agent: Pinterest

User-agent: Plukkie

User-agent: Qwantify

User-agent: Rambler

User-agent: SeznamBot

User-agent: Sosospider

User-agent: Slurp

User-agent: Sogou blog

User-agent: Sogou inst spider

User-agent: Sogou News Spider

User-agent: Sogou Orion spider

User-agent: Sogou spider2

User-agent: Sogou web spider

User-agent: SputnikBot

User-agent: Teoma

User-agent: Twitterbot

User-agent: wotbox

User-agent: yacybot

User-agent: Yandex

User-agent: YandexMobileBot

User-agent: Yeti

User-agent: YioopBot

User-agent: yoozBot

User-agent: YoudaoBot

Disallow: /wp-admin/

User-agent: *

Disallow: /
B
TLS Certificate Expiry & Recommendations
179 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
4 A records, 43 ms lookup
PASS
4 A records, 43 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 13.227.107.9, 13.227.107.46, 13.227.107.13, 13.227.107.12
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-112.awsdns-14.com, ns-1423.awsdns-49.org, ns-1777.awsdns-30.co.uk, ns-855.awsdns-42.net
Info::
6 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: 43 ms
Got: 43 ms
A13.227.107.9, 13.227.107.46, 13.227.107.13, 13.227.107.12
AAAA
CNAME
NSns-112.awsdns-14.com, ns-1423.awsdns-49.org, ns-1777.awsdns-30.co.uk, ns-855.awsdns-42.net
MX
40 aspmx.l.google.com
50 alt1.aspmx.l.google.com
60 alt2.aspmx.l.google.com
70 aspmx2.googlemail.com
80 aspmx3.googlemail.com
90 aspmx4.googlemail.com
TXT
MS=ms78214898
adobe-idp-site-verification=c08578d97fc1bb012e79e6bc3c29f7d6458670b636bf1143a707...
d1x0alisu9v9bg.cloudfront.net
fktlhibfsv149gibvln6ipf45h
google-site-verification=h020xCrrhiNgm86-ntglLTvnI_wNWgRHO036eF7zKLc
identrust_validate=LZdS0KuNmDCqbXaWYVvB8j8fvWQhIliA2n+ohW5C/7Qi
miro-verification=53bf5ccd47cb6239fe5cf14c3b328050dd5679ac
postman-domain-verification=8dcd461c89102c435b68ccaac00f9758d15c5fa3d88f54679a46...
uf84s1envst5gcn4vifmkrl5kd
SPF v=spf1 include:amazonses.com include:_spf.google.com include:_spf.salesforce.com...
wrike-verification=MjEzNzM3NjpmNGM0ZGMzZjcxMzYyNmE4NjM3ZTNiMjA1NTgxNmNiNjc4YWVhN...
CAALookup not available with standard resolver
Resolved in 43 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), 500 ms total
PASS
1 redirect(s), 500 ms total
Info::
Single redirect
Got: https://meraki.com → https://meraki.cisco.com/ (301)
Info::
Cross-domain redirect detected

https://meraki.com

10 ms · HTTP/1.1

301

https://meraki.cisco.com/

489 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://meraki.com30110 msHTTP/1.1AmazonS3
2https://meraki.cisco.com/200489 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.meraki.com/
200https://meraki.com/

Preferred variant: non-www

HTTP → HTTPS

301http://meraki.com/ https://meraki.cisco.com/

Consistent

A+
Domain Intelligence
meraki.com — via MarkMonitor Inc., 23 years, 7 months old, hosted on AWS
PASS
meraki.com — via MarkMonitor Inc., 23 years, 7 months old, hosted on AWS
Info::
Domain registered until Jan 6, 2028 (1 years, 9 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: 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

570 days

January 6, 2028

SSL certificate

179 days

Issued by Amazon

Domain age

23 years, 7 months

Registered January 6, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.227.107.9

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created January 6, 2003 (23 years, 7 months ago)
Expires January 6, 2028 (1 years, 9 months)
Last Updated March 4, 2019
Name Servers ns-112.awsdns-14.com, ns-1423.awsdns-49.org, ns-1777.awsdns-30.co.uk, ns-855.awsdns-42.net
DNSSEC Not enabled
Hosting
IP Address 13.227.107.9
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.6s)

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

Connection waterfall

DNS Lookup 2 ms TCP Connect 2 ms TLS Handshake 6 ms Server Processing 4 ms Content Transfer 0 ms
A+
CDN & Delivery
AWS CloudFront (Hit from cloudfront)
PASS
AWS CloudFront (Hit from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: GRU3-P11)
Got: x-amz-cf-id: TK3O1ejdWiCN2bljG0tD6-VhDu35c_P1-4Qw3w6DERgotgHSjmVwVg==
Info::
CDN cache status: Hit from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: TK3O1ejdWiCN2bljG0tD6-VhDu35c_P1-4Qw3w6DERgotgHSjmVwVg==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback