Skip to content
https://scitation.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
6 PASS 2 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
TLS Certificate Expiry & Recommendations
89 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

89
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, 119 ms lookup
PASS
1 A records, 119 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 20.85.172.21
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
10 nameserver(s) configured
Got: ns31.constellix.com, ns51.constellix.net, ns3-37.azure-dns.org, ns41.constellix.net, ns61.constellix.net, ns11.constellix.com, ns4-37.azure-dns.info, ns21.constellix.com, ns1-37.azure-dns.com, ns2-37.azure-dns.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: 119 ms
Got: 119 ms
A20.85.172.21
AAAA
CNAME
NSns31.constellix.com, ns51.constellix.net, ns3-37.azure-dns.org, ns41.constellix.net, ns61.constellix.net, ns11.constellix.com, ns4-37.azure-dns.info, ns21.constellix.com, ns1-37.azure-dns.com, ns2-37.azure-dns.net
MX
0 scitation-org.mail.protection.outlook.com
TXT
5wxymryrm887h7j16tprcfpdnb6dnmb4
facebook-domain-verification=fay9p1xb3fasvr5ipfbyp145q6py1s
SPF v=spf1 mx ip4:212.54.151.65/32 ip4:212.54.151.66/32 ip4:52.144.53.65/32 ip4:52.1...
google-site-verification=P1RVx9kY_5qYglK-xfHrN51vMZNnqIjtSnAok7yDtR0
CAALookup not available with standard resolver
Resolved in 119 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), 194 ms total
PASS
1 redirect(s), 194 ms total
Info::
Single redirect
Got: https://scitation.org → https://pubs.aip.org/ (301)
Info::
Cross-domain redirect detected

https://scitation.org

154 ms · HTTP/1.1

301

https://pubs.aip.org/

41 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://scitation.org301154 msHTTP/1.1Microsoft-IIS/10.0
2https://pubs.aip.org/40341 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1195 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references 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

robots.txt 200 OK
Size 1195 B Sitemaps referenced 6 User-agents 008, * Blocking No — crawling allowed

User-agent: 008

Disallow: /


User-agent: *

Disallow: /bin/

Disallow: /config/

Disallow: /app_data/

Disallow: /dlls/

Disallow: /App_Themes/

Disallow: /signin.aspx

Disallow: /searchresults.aspx

Disallow: /search-results

Disallow: /advancedsearch.aspx

Disallow: /advanced-search

Disallow: /DownloadFile/

Disallow: /downloadimage.aspx

Disallow: /Citation/Download

Disallow: /Shibboleth.sso/

Disallow: /SignInShibboleth.aspx

Disallow: /lookup/external-ref

Disallow: /user/logout

Disallow: /cgi/pmidlookup

Disallow: /Themes/Client/app/img/favicons/manifest.json

Disallow: /lookup/google-scholar

Disallow: /store/*

Allow: /cassette.axd/stylesheet/

Allow: /cassette.axd/script/

Allow: /cassette.axd/manifest.xml

Disallow: /*.axd

Disallow: /specificToClient1/

Sitemap: https://pubs.aip.org/data/sitemap/Site_1/sitemap_books_site1.xml

Sitemap: https://pubs.aip.org/data/sitemap/Site_1/sitemap_gbos_site1.xml

Sitemap: https://pubs.aip.org/data/sitemap/Site_1000143/sitemap.xml

Sitemap: https://pubs.aip.org/data/sitemap/Site_1000145/sitemap.xml

Sitemap: https://pubs.aip.org/data/sitemap/Site_1000147/sitemap.xml

Sitemap: https://pubs.aip.org/data/sitemap/sitemap.xml


sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.scitation.org/
200https://scitation.org/

Preferred variant: non-www

HTTP → HTTPS

301http://scitation.org/ https://scitation.org/

Consistent

A+
Domain Intelligence
scitation.org — via Network Solutions, LLC, 23 years, 4 months old, hosted on Microsoft Azure
PASS
scitation.org — via Network Solutions, LLC, 23 years, 4 months old, hosted on Microsoft Azure
Info::
Domain registered until Apr 2, 2028 (1 years, 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: Network Solutions, LLC
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: Microsoft Azure
Got: AS8075
Domain expiry

626 days

April 2, 2028

SSL certificate

89 days

Issued by Let's Encrypt

Domain age

23 years, 4 months

Registered April 2, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

20.85.172.21

Registrar

Network Solutions, LLC

Unlocked 10 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 Network Solutions, LLC
Created April 2, 2003 (23 years, 4 months ago)
Expires April 2, 2028 (1 years, 11 months)
Last Updated February 6, 2025
Name Servers ns3-37.azure-dns.org, ns1-37.azure-dns.com, ns11.constellix.com, ns2-37.azure-dns.net, ns21.constellix.com, ns31.constellix.com, ns4-37.azure-dns.info, ns41.constellix.net, ns51.constellix.net, ns61.constellix.net
DNSSEC Not enabled
Hosting
IP Address 20.85.172.21
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: rdap (0.2s)

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 152 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
119 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
7 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.
152 ms
Total Time Total request time from DNS lookup through full response.
152 ms

Connection waterfall

DNS Lookup 119 ms TCP Connect 7 ms TLS Handshake 10 ms Server Processing 16 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