Skip to content
https://researchgate.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 293 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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 293 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /cdn-cgi/
Disallow: /connector/
Disallow: /plugins.
Disallow: /firststeps.
Disallow: /publicliterature.PublicLiterature.search.html
Disallow: /lite.publication.PublicationRequestFulltextPromo.requestFulltext.html
Allow: /signup.SignUp.html$
Disallow: /signup.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.researchgate.net/
200https://researchgate.net/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://researchgate.net/ https://researchgate.net/

Consistent

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

Certificate validity

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

Recommended actions

  • 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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: GRU)
Got: cf-ray: 9ed4d17b4cc86278-GRU
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9ed4d17b4cc86278-GRU
A+
DNS Records
2 A records, 11 ms lookup
PASS
2 A records, 11 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.41.9, 172.64.146.247
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:4401::ac40:92f7, 2606:4700:4403::6812:2909
Info::
2 nameserver(s) configured
Got: marty.ns.cloudflare.com, val.ns.cloudflare.com
Info::
5 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: 11 ms
Got: 11 ms
A104.18.41.9, 172.64.146.247
AAAA2606:4700:4401::ac40:92f7, 2606:4700:4403::6812:2909
CNAME
NSmarty.ns.cloudflare.com, val.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
apple-domain-verification=1zVGDn699lBJWe3h
atlassian-domain-verification=Nad6ba1ysA1mdnvoY0zYwoRwv6nBwSBawy/Xaexh3Vf9DcC0a7...
google-site-verification=adDX9Qsrt8PjtLYlL3wfJJVp_QvS36jMwtcjEPd4J9Q
google-site-verification=o6Zn1HIYOJ47s1qpx6D1NYJiRORsOBrWWIKgCHozu0g
SPF v=spf1 ip4:209.15.209.64/27 ip4:209.15.214.192/28 ip4:209.15.243.112/28 ip4:209....
CAALookup not available with standard resolver
Resolved in 11 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), 93 ms total
PASS
1 redirect(s), 93 ms total
Info::
Single redirect
Got: https://researchgate.net → https://www.researchgate.net/ (301)
Info::
WWW normalization redirect

https://researchgate.net

22 ms · HTTP/1.1

301

https://www.researchgate.net/

71 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://researchgate.net30122 msHTTP/1.1cloudflare
2https://www.researchgate.net/20071 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2606:4700:4401::ac40:92f7, 2606:4700:4403::6812:2909
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:4700:4401::ac40:92f7, 2606:4700:4403::6812:2909 Connection Reachable (2 ms)
A+
Domain Intelligence
researchgate.net — via Mesh Digital Limited, 18 years, 5 months old
PASS
researchgate.net — via Mesh Digital Limited, 18 years, 5 months old
Info::
Domain registered until Feb 8, 2027 (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: Mesh Digital Limited
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.
Domain expiry

210 days

February 8, 2027

SSL certificate

34 days

Issued by Google Trust Services

Domain age

18 years, 5 months

Registered February 8, 2008

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:4401::ac40:92f7

Registrar

Mesh Digital Limited

Unlocked 2 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 Mesh Digital Limited
Created February 8, 2008 (18 years, 5 months ago)
Expires February 8, 2027 (9 months)
Last Updated February 7, 2026
Name Servers marty.ns.cloudflare.com, val.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:4401::ac40:92f7
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 6 ms TCP Connect 2 ms TLS Handshake 10 ms Server Processing 5 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