Skip to content
https://proquest.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 2491 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 2491 B Sitemaps referenced 0 User-agents ChatGPT-User, OAI-SearchBot, *, GPTBot Blocking No — crawling allowed

User-agent: *

Disallow: /url/
Disallow: /AppleWebKit/
Disallow: /a11y/
Disallow: /input/
Disallow: /output/
Disallow: /indexol.sourcetypessearch.expandedbasicsearchbox.searchterm
Disallow: /docview/*PQ/1
Disallow: /*.captureproxyhost:
Disallow: /widget/
Disallow: /*.docviewusetools
Disallow: /*.docviewanalytics
Disallow: /*.pdfdocusetools
Disallow: /*.documentimageusetools
Disallow: /previewunavailable
Disallow: /*.fulltext:hidefulltext

Disallow: /honeypot

Disallow: /help/

Disallow: /*.similardocuments

Disallow: /*.pagelayout.popuplocaleswitcher

Disallow: /*:interdocimagesevent

Disallow: /*.progressivedisplay

Disallow: /*.loginoverlay

   
Disallow: /*:allsaveoptions

Disallow: */shibbolethlogin

Disallow: */error/
Disallow: */errorpage/

Disallow: /*:hidebannerevent

Disallow: /%

Disallow: /c/
Disallow: /C/


Disallow: */indexinglinkhandler

Disallow: */indexingvolumeissuelinkhandler


Disallow: /login

Disallow: /*.quicksearchbox

Disallow: /*.accesstofulltextlinks.*

Disallow: /congressional

Disallow: /go/
Disallow: /about/

Disallow: /pubidlinkhandler/



Disallow: /products-services/
Allow:    /products-services/*/se-2

Disallow: /openview/

Disallow: /blog/
Allow:    /blog/*/se-2

Disallow: /embed/
Allow:    /embed/*/se-2

Disallow: /professional/

Disallow: /en-US/

Disallow: /products_pq/
Allow:    /products_pq/*/se-2

Disallow: /pdpq/
Allow:    /pdpq/*/se-2

Disallow: /documents/
Allow:    /documents/*/se-2

Disallow: /company/
Allow:    /company/*/se-2

Disallow: /libraries/
Allow:    /libraries/*/se-2

Disallow: /*?accountid=*
Disallow: /*&accountid=*

Disallow: /*?username=

Disallow: /*.quicksearchbox:

Disallow: /*.pagelayout.pendo

Disallow: /APAC-JP/

Disallow: /histvault?
Disallow: /histvault/

Disallow: /*:externallink


Disallow: .html$
Disallow: .html?

Disallow: .shtml$

Disallow: /ebdetailsview

Disallow: /*.hitnavigationswitch:

Disallow: /historyvault

Disallow: /customer-care/tools-resources/

Disallow: /runSearch

Disallow: /*.pagelayout:

Disallow: /en/
Disallow: /Documents/

Disallow: /congcomp/getdoc

Disallow: /myresearch/

Disallow: /docview.accesstofulltextlinks.externallink_0:

Disallow: /docprintview/

Disallow: /docview.suggestedsources.suggestedsourcesbelowfulltext

Disallow: /docview.suggestedsources:suggesteditemszoneexpandbelowfulltext

Disallow: /docview.fulltext:displayfulltext;jsessionid=

User-agent: GPTBot	
Disallow: /

User-agent: ChatGPT-User	
Disallow: /

User-agent: OAI-SearchBot	
Allow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Connection waterfall

DNS Lookup 30 ms TCP Connect 106 ms TLS Handshake 654 ms Server Processing 95 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
145 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

145
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
1 A records, 92 ms lookup
PASS
1 A records, 92 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 165.215.200.228
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: sunny.ns.cloudflare.com, hugh.ns.cloudflare.com
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: 92 ms
Got: 92 ms
A165.215.200.228
AAAA—
CNAME—
NSsunny.ns.cloudflare.com, hugh.ns.cloudflare.com
MX
10 proquest-com.mail.protection.outlook.com
TXT
amazon-business-verification=70c7ffd7e18a145369a51e368b0d584a89c56bab9d8a4cb50f1...
atlassian-domain-verification=uqUUHlogFKYYZxEZ3cJ6ZetyGYMPDuIMa3yrn6AosE3NBvgASM...
cloudflare-verify.stage-about.proquest.com=315325281-371351941
_esxh5enpumowvh733k8s6whma4920u4
status-page-domain-verification=yclqkwj0mpym
apple-domain-verification=21QhpQJq3KYswHDm
h7/xk1ifehbrC55Z96TBPIRBIwg6+1HqZJAgkkmNISC53iYO346J4VCWECpSqJV5DNYzY7sa4LSXmEZ7...
SPF v=spf1 include:spf.protection.outlook.com include:spf.proquest.com include:amazo...
google-site-verification=9Z1phgU6Xofo9g2tfjqL2cfLKuOrCTYkogANFdBnYGQ
awverify.stage-about.proquest.com=proq01mstrafi66prep.azurewebsites.net
_u17zd5qnng21ra315x72d6la4wu1e8t
MS=ms92939022
ciscocidomainverification=1b0a8eb7b0ba19699a550761d081ebe5826992a0845f9395383fff...
MS=ms88188049
onetrust-domain-verification=3b4afe4244bd4d6699f3c0f3ed97964a
b1y76hhcw6093hphb4f8kng9bmcq11k4
vmware-cloud-verification-c0d82e6e-3b5a-417a-a524-265ec7b335c4
amazonses:6PF+w3CBqkZz5GxGNbahAhEfJ6SEnh9tpn8W9ZMOPbI=
docusign=0c28423b-da0a-4c32-bb63-6940a33a4b1e
citrix-verification-code=038de96b-32b2-46fa-bf8f-1aaef02533ee
_upgt3j3ftad6172m62pxq92g4jerhsx
CAALookup not available with standard resolver
Resolved in 92 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

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), 621 ms total
PASS
1 redirect(s), 621 ms total
Info::
Single redirect
Got: https://proquest.com → https://www.proquest.com/ (301)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.proquest.com/
Info::
Redirect overhead: 621 ms total
Got: 621 ms

https://proquest.com

287 ms · HTTP/1.1

301

https://www.proquest.com/

333 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://proquest.com301287 msHTTP/1.1
2https://www.proquest.com/302333 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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

302https://www.proquest.com/
200https://proquest.com/

Preferred variant: non-www

HTTP → HTTPS

301http://proquest.com/ → https://www.proquest.com/

Consistent

A+
Domain Intelligence
proquest.com — via MarkMonitor Inc., 30 years, 6 months old, hosted on PROQUEST - PROQUEST, LLC, US
PASS
proquest.com — via MarkMonitor Inc., 30 years, 6 months old, hosted on PROQUEST - PROQUEST, LLC, US
Info::
Domain registered until Mar 24, 2027 (11 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: PROQUEST - PROQUEST, LLC, US
Got: AS40675
Domain expiry

283 days

March 24, 2027

SSL certificate

145 days

Issued by DigiCert Inc

Domain age

30 years, 6 months

Registered March 23, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

PROQUEST - PROQUEST, LLC, US

ASN AS40675

165.215.200.228

Registrar

MarkMonitor Inc.

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 MarkMonitor Inc.
Created March 23, 1996 (30 years, 6 months ago)
Expires March 24, 2027 (11 months)
Last Updated February 20, 2026
Name Servers hugh.ns.cloudflare.com, sunny.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 165.215.200.228
ASN AS40675 (PROQUEST - PROQUEST, LLC, US)
Provider PROQUEST - PROQUEST, LLC, US
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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback