Skip to content
https://pbase.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from New York, United Stated
200 OK
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

C
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 3701 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 3701 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
<html lang="en-US"><head>
<title>pbase Artist romee</title>
<link rel="stylesheet" type="text/css" href="https://ap1.pbase.com/styles/gallery2.v4.css">
<link rel="stylesheet" type="text/css" href="https://ap1.pbase.com/styles/comments.v2.css">
<link rel="stylesheet" type="text/css" href="https://ap1.pbase.com/styles/gallery2.v4.css">
<link rel="alternate" href="https://feeds.pbase.com/feeds/robots/galleries.atom" title="romee's Gallery Updates" type="application/atom+xml" />
</head><body>
<TABLE border=0 cellspacing=0 cellpadding=0 width="100%"><tr>
<td><A HREF="https://pbase.com" target="_top" title="pbase photos"><IMG src="https://ap1.pbase.com/site/m_pbase.gif" border=0 alt="photo sharing and upload"></A></td>
<td><A HREF="https://pbase.com/galleries" target="_top" title="recent picture uploads"><IMG src="https://ap1.pbase.com/site/m_g.gif" border=0 alt="picture albums"></A></td>
<td><A HREF="https://forum.pbase.com" target="_top" title="photography discussion forums"><IMG src="https://ap1.pbase.com/site/m_f.gif" border=0 alt="photo forums"></A></td>
<td><A HREF="https://pbase.com/search" target="_top" title="pbase photo search"><IMG src="https://ap1.pbase.com/site/m_s.gif" border=0 alt="search pictures"></A></td>
<td width="100%"><A HREF="https://pbase.com/galleries?view=popular" target="_top" title="popular photos"><IMG src="https://ap1.pbase.com/site/m_sp.gif" border=0 height="28" width="100%" alt="popular photos"></a></td>

<td><A HREF="https://pbase.com/help" target="_top" title="give me some help"><IMG src="https://ap1.pbase.com/site/m_h.gif" border=0 alt="photography help"></A></td>
<td><A HREF="https://pbase.com/login" target="_top" title="login to pbase"><IMG src="https://ap1.pbase.com/site/m_l.gif" border=0 alt="login"></A></td>
</tr></table>
<!-- END menu bar -->

<table border=0 width="100%">
<tr>
<td align=left >
<b>
romee
 |
profile
 | 
<a HREF="/robots/guestbook" title="goto robots's guestbook">guestbook</a>
 | 
<a href="/robots" title="goto robots's galleries">all galleries</a>
 | 
<a href="/robots/root&view=recent" title="robots's recent galleries" rel="nofollow">recent</a>
</b>
</td>
</tr>
</table>
<br>

<!-- begin box -->
<TABLE cellSpacing=0 cellPadding=1  border=0 width="98%" align="center">
  <TBODY>
  <TR><TD class="ma">Profile for romee
    <TABLE cellSpacing=0 cellPadding=2 width="100%" border=0 bgcolor="#ffffff">
      <TBODY>
      <tr><td class="wb">

<TABLE border=0 width="100%">
<tr><td valign="top">

<TABLE border=0>
<tr>
<td class=mi>Name</td>
<td class=wb>romee <span class="small">(joined 11-Mar-2026)
</span>
</td>
</tr>

<tr>
<td class=mi>Username</td>
<td class=wb>robots</td>
</tr>

<tr>
<td class=mi>Location</td>
<td class=wb>United States</td>
</tr>
</table>
</td>
<td align=right valign=top class=wb>
<a href="/world/united_states" alt="united_states">
<IMG class=thumbnail src="https://a4.pbase.com/u38/world_images/100/24960632.uslgflag.jpg" WIDTH=100 HEIGHT=53 border=2 alt="united_states" loading="lazy" >
</a>
<br>
United States
</td>
</tr>
</table>

      </td></tr>
      </TBODY>
    </TABLE>
  </TD></TR>
    
  </TBODY>
</TABLE>
<!-- end box-->

<!-- begin box -->
<TABLE cellSpacing=0 cellPadding=1  border=0 width="98%" align="center">
  <TBODY>
  <TR><TD class="mi">Statistics
    <TABLE cellSpacing=0 cellPadding=2 width="100%" border=0 bgcolor="#ffffff">
      <TBODY>
      <tr><td class="wb">

romee has no images online.<br>These pages have been viewed a total of <b>0</b> times.  
<br>
<br>
<a href="/robots/guestbook">View Guestbook</a> : 
No guestbook messages.
<br><br>
      </td></tr>
      </TBODY>
    </TABLE>
  </TD></TR>
    
  </TBODY>
</TABLE>
<!-- end box-->
<br>

</body>
</html>
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
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.pbase.com/
200https://pbase.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://pbase.com/ https://pbase.com:443/

Consistent

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
2 A records, 5 ms lookup
PASS
2 A records, 5 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 52.2.183.171, 52.204.6.113
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1451.awsdns-53.org, ns-1887.awsdns-43.co.uk, ns-47.awsdns-05.com, ns-942.awsdns-53.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: 5 ms
Got: 5 ms
A52.2.183.171, 52.204.6.113
AAAA
CNAME
NSns-1451.awsdns-53.org, ns-1887.awsdns-43.co.uk, ns-47.awsdns-05.com, ns-942.awsdns-53.net
MX
10 inbound-smtp.us-east-1.amazonaws.com
TXT
brave-ledger-verification=9d2a2241be4498e61ad5e5b1eb02fc4db5f403b55914d7ce8b8d0a...
SPF v=spf1 a mx ip4:52.200.144.14 include:mail.zendesk.com -all
SPF v=spf1 include:amazonses.com -all
CAALookup not available with standard resolver
Resolved in 5 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://pbase.com

https://pbase.com

82 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://pbase.com20082 msHTTP/1.1Apache/2.4.37 (Amazon) mod_perl/2.0.7 Perl/v5.16.3
A+
Domain Intelligence
pbase.com — via Network Solutions, LLC, 27 years, 1 months old, hosted on AWS
PASS
pbase.com — via Network Solutions, LLC, 27 years, 1 months old, hosted on AWS
Info::
Domain registered until Aug 10, 2030 (4 years, 4 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: AWS
Got: AS14618
Domain expiry

1516 days

August 10, 2030

SSL certificate

113 days

Issued by Amazon

Domain age

27 years, 1 months

Registered August 10, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

52.204.6.113

Registrar

Network Solutions, LLC

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 Network Solutions, LLC
Created August 10, 1999 (27 years, 1 months ago)
Expires August 10, 2030 (4 years, 4 months)
Last Updated June 10, 2025
Name Servers ns-1451.awsdns-53.org, ns-1887.awsdns-43.co.uk, ns-47.awsdns-05.com, ns-942.awsdns-53.net
DNSSEC Not enabled
Hosting
IP Address 52.204.6.113
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.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

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

Connection waterfall

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