Skip to content
https://www.instagram.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
3
REVIEW
1
PASS
5
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
9
5 PASS 1 REVIEW 3 FIX
D
Crawlability
Action
robots.txt present, no sitemap
FIX
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 5608 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::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references 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

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt 200 OK
Size 5608 B Sitemaps referenced 7 User-agents Applebot-Extended, uptimerobot, LinkedInBot, seznambot, TelegramBot, Twitterbot, GPTBot, PetalBot, Pinterestbot, teoma, Googlebot, Googlebot-News, ClaudeBot, PerplexityBot, Scrapy, YaK, Applebot, Googlebot-Video, Slurp, *, Amazonbot, Brightbot, Google-Extended, viberbot, Screaming Frog SEO Spider, Yeti, Bingbot, Discordbot, facebookexternalhit, Google-InspectionTool, msnbot, Yandex, DuckDuckBot, Googlebot-Image Blocking Yes — all crawlers blocked
# Notice: Collection of data on Instagram through automated means is
# prohibited unless you have express written permission from Instagram
# and may only be conducted for the limited purpose contained in said
# permission.
# All authorized user-agents listed on this page must comply with Meta’s
# Automated Data Collection Terms available at:
# https://www.facebook.com/legal/automated_data_collection_terms
User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Brightbot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: PetalBot
Disallow: /

User-agent: Scrapy
Disallow: /

User-agent: uptimerobot
Disallow: /

User-agent: viberbot
Disallow: /

User-agent: YaK
Disallow: /

User-agent: Yandex
Disallow: /

User-agent: Yeti
Disallow: /

User-agent: Applebot
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: Bingbot
Disallow: /*/c/
Disallow: /*/comments/
Disallow: /*/liked_by/
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: Discordbot
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: DuckDuckBot
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: facebookexternalhit
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: Googlebot
Disallow: /*/c/
Disallow: /*/comments/
Disallow: /*/liked_by/
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: Googlebot-Image
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: Googlebot-Video
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: Googlebot-News
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: Google-InspectionTool
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: LinkedInBot
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: msnbot
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: Pinterestbot
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: Screaming Frog SEO Spider
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: seznambot
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: Slurp
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: teoma
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: TelegramBot
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: Twitterbot
Disallow: /accounts/login/*?next=
Disallow: /ajax/
Disallow: /client_error/
Disallow: /direct/
Disallow: /logging/
Disallow: /publicapi/
Disallow: /qp/batch_fetch_web/
Disallow: /query/

User-agent: *
Disallow: /

Sitemap: https://www.instagram.com/sitemap/ig_seo_guide_sitemap.xml.gz
Sitemap: https://www.instagram.com/sitemap/ig_seo_images_sitemap.xml.gz
Sitemap: https://www.instagram.com/sitemap/ig_seo_profile_sitemap.xml.gz
Sitemap: https://www.instagram.com/sitemap/ig_seo_profile_sitemap_small_accounts.xml.gz
Sitemap: https://www.instagram.com/sitemap/ig_seo_location_sitemap.xml.gz
Sitemap: https://www.instagram.com/sitemap/ig_seo_audio_sitemap.xml.gz
Sitemap: https://www.instagram.com/sitemap/dim_ig_logged_out_web_keyword_ent.xml.gz


sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

D
TLS Certificate Expiry & Recommendations
Action
8 days until leaf cert expires — 4 issues to address
FIX

Certificate validity

8
days left
0d 30d 60d 90d+
Renew urgently — under 14 days remaining

Recommended actions

  • Renew certificate — 8 days remaining
  • 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
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.

B
DNS Records
1 A records, 231 ms lookup
REVIEW
1 A records, 231 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 157.240.226.174
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a03:2880:f248:1e5:face:b00c:0:4420
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: z-p42-instagram.c10r.instagram.com
Info::
No NS records found
Info::
No MX records — email not configured via DNS
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
Warning::
DNS resolution is slow (231 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 231 ms
A157.240.226.174
AAAA2a03:2880:f248:1e5:face:b00c:0:4420
CNAMEz-p42-instagram.c10r.instagram.com
NS
MX
TXT
SPF v=spf1 a ~all
CAALookup not available with standard resolver
Resolved in 231 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

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.

Why this matters

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

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.instagram.com

https://www.instagram.com

228 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.instagram.com200228 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a03:2880:f248:1e5:face:b00c:0:4420
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a03:2880:f248:1e5:face:b00c:0:4420 Connection Reachable (1 ms)
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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Preferred variant: www

HTTP → HTTPS

301http://www.instagram.com/ https://www.instagram.com/

Consistent

A+
Domain Intelligence
instagram.com — via RegistrarSafe, LLC, 22 years, 1 months old
PASS
instagram.com — via RegistrarSafe, LLC, 22 years, 1 months old
Info::
Domain registered until Jun 4, 2034 (8 years, 3 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: RegistrarSafe, LLC
Domain expiry

2848 days

June 4, 2034

SSL certificate

8 days

Issued by DigiCert Inc

Domain age

22 years, 1 months

Registered June 4, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a03:2880:f248:1e5:face:b00c:0:4420

Registrar

RegistrarSafe, LLC

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar RegistrarSafe, LLC
Created June 4, 2004 (22 years, 1 months ago)
Expires June 4, 2034 (8 years, 3 months)
Last Updated June 25, 2025
Name Servers a.ns.instagram.com, b.ns.instagram.com, c.ns.instagram.com, d.ns.instagram.com
DNSSEC Not enabled
Hosting
IP Address 2a03:2880:f248:1e5:face:b00c:0:4420
Data source: rdap (1.1s)

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

A
HTTP Probe Timing
Total 607 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
11 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.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
252 ms
Total Time Total request time from DNS lookup through full response.
607 ms

Connection waterfall

DNS Lookup 11 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 236 ms Content Transfer 356 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback