Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/4 IPs match cert SANREVIEW
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BDomain Intelligencepearreview.com — via Spaceship, Inc., 2 years old, hosted on CloudflareREVIEW
4 days
August 30, 2026
79 days
Issued by Google Trust Services
2 years
Registered August 30, 2024
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS13335
172.67.164.214
Spaceship, Inc.
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
This domain expires on August 30, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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
BTLS Certificate Expiry & Recommendations79 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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
BOperational Status PageNo status page link detectedREVIEW
ADNS Records2 A records, 15 ms lookupPASS
| A | 172.67.164.214, 104.21.10.247 |
| AAAA | 2606:4700:3033::ac43:a4d6, 2606:4700:3035::6815:af7 |
| CNAME | — |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 14ms across 3 resolvers (spread 19ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
HTTPS://www.pearreview.com
207 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | HTTPS://www.pearreview.com | 200 | 207 ms | HTTP/1.1 | cloudflare |
A+Crawlabilityrobots.txt present, sitemap with 38 URLsPASS
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
<script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1502173011299631"
crossorigin="anonymous"></script><center>
<script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1502173011299631"
crossorigin="anonymous"></script>
<!-- erge444 -->
<ins class="adsbygoogle"
style="display:block"
data-ad-client="ca-pub-1502173011299631"
data-ad-slot="7009662871"
data-ad-format="auto"
data-full-width-responsive="true"></ins>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>
</center>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="de" lang="de" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<title>Startseite | PearReview - Review-Tool</title>
<link rel="canonical" href="https://pearreview.com" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<link rel="shortcut icon" href="sites/all/themes/PearReview/favicon.ico" type="image/x-icon"/>
<link type="text/css" rel="stylesheet" media="all" href="modules/node/node-G.css"/>
<link type="text/css" rel="stylesheet" media="all" href="modules/poll/poll-G.css"/>
<link type="text/css" rel="stylesheet" media="all" href="modules/system/defaults-G.css"/>
<link type="text/css" rel="stylesheet" media="all" href="modules/system/system-G.css"/>
<link type="text/css" rel="stylesheet" media="all" href="modules/system/system-menus-G.css"/>
<link type="text/css" rel="stylesheet" media="all" href="modules/user/user-G.css"/>
<link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/zen/zen/tabs-G.css"/>
<link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/PearReview/messages-G.css"/>
<link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/zen/zen/block-editing-G.css"/>
<link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/zen/zen/wireframes-G.css"/>
<link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/PearReview/zen-G.css"/>
<link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/PearReview/layout-fixed-G.css"/>
<link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/PearReview/style-G.css"/>
<link type="text/css" rel="stylesheet" media="all" href="sites/all/themes/PearReview/jquery.lightbox-0.5-G.css"/>
<!--[if IE]>
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/themes/zen/zen/ie.css?G" />
<![endif]-->
<script type="text/javascript" src="misc/jquery-G.js"></script>
<script type="text/javascript" src="misc/drupal-G.js"></script>
<script type="text/javascript" src="sites/default/files/languages/de_1ad018fc22722f19c63dba9334d35589-G.js"></script>
<script type="text/javascript" src="sites/all/themes/PearReview/js/jquery-G.js"></script>
<script type="text/javascript" src="sites/all/themes/PearReview/js/jquery.lightbox-0.5-G.js"></script>
<script type="text/javascript" src="sites/all/themes/PearReview/js/jquery.color-G.js"></script>
<script type="text/javascript">
<!--//--><![CDATA[//><!--
jQuery.extend(Drupal.settings, { "basePath": "/" });
//--><!]]>
</script>
<script type="text/javascript">
$(document).ready(function(){
//lightbox
var settings = {
imageLoading: 'http://www.pearreview.com/sites/all/themes/PearReview/images/lightbox-ico-loading.gif',
imageBtnPrev: 'http://www.pearreview.com/sites/all/themes/PearReview/images/lightbox-btn-prev.gif',
imageBtnNext: 'http://www.pearreview.com/sites/all/themes/PearReview/images/lightbox-btn-next.gif',
imageBtnClose: 'http://www.pearreview.com/sites/all/themes/PearReview/images/lightbox-btn-close.gif',
imageBlank: 'http://www.pearreview.com/sites/all/themes/PearReview/images/lightbox-blank.gif'
};
$("#content a[href$='.jpg']").lightBox(settings);
$("#content a[href$='.png']").lightBox(settings);
$("#content a[href$='.gif']").lightBox(settings);
$("#content a[href$='.jpeg']").lightBox(settings);
//animate input fields
var input = $("form input[class!=form-submit]");
input.focus(function(){
$(this).animate({backgroundColor: "#d9e880"}, "slow")
});
input.blur(function(){
$(this).animate({backgroundColor: "#ffffff"}, "slow")
});
//animate textarea
var textarea = $("form textarea");
textarea.focus(function(){
$(this).animate({backgroundColor: "#d9e880"}, "slow")
});
textarea.blur(function(){
$(this).animate({backgroundColor: "#ffffff"}, "slow")
});
// Add pdf icons to pdf links
$("a[href$='.pdf']").addClass("pdf");
// Add exe icons to pdf links
$("a[href$='.exe']").addClass("exe");
// Add dmg icons to pdf links
$("a[href$='.dmg']").addClass("dmg");
// Add jar icons to pdf links
$("a[href$='.jar']").addClass("jar");
// Add xml icons to pdf links
$("a[href$='.xml']").addClass("xml");
// Add zip icons to pdf links
$("a[href$='.zip']").addClass("zip");
});
</script>
</head>
<body class="front not-logged-in node-type-page one-sidebar sidebar-right">
<div id="page"><div id="page-inner">
<a name="top" id="navigation-top"></a>
<div id="header"><div id="header-inner" class="clear-block">
<div id="head_logo"><a class="logo_link" href="/" title="Startseite" rel="home"></a></div>
<div id="head_download"><a class="download_link" href="download" title="Download PearReview"></a></div>
<div class="clear"></div>
</div></div> <!-- /#header-inner, /#header -->
<div id="main"><div id="main-inner" class="clear-block with-navbar">
<div id="content"><div id="content-inner">
<div id="content-header">
<h1 class="title">Startseite</h1>
</div> <!-- /#content-header -->
<div id="content-area">
<div id="node-1" class="node node-type-page"><div class="node-inner">
<div class="content">
<p>PearReview ist ein Assistent zum Planen und Durchführen von Reviews. Unter einem Review wird hier speziell das technische Review im Software-Bereich (*) verstanden. PearReview lässt sich allerdings problemlos auch in anderen Bereichen einsetzten.</p>
<p>PearRview ist eine Open Source Software, die im Rahmen des Software-Praktikums an der Universität Stuttgart entstanden ist und kann kostenlos im privaten und kommerziellen Gebrauch eingesetzt werden.</p>
<p>PearReview unterstützt das Planen von Review-Sitzungen, erlaubt es den Teilnehmern bestimmte Rollen (Moderator, Notar, Gutachter, Autor und Kunde) zu zuweisen und schriftliche Einladungen in Form von PDF-Dokumenten für sie zu erstellen.<br/>
Es ist möglich den Gutachtern bestimmte Aspekte zu zuweisen, auf die sie den Prüfling untersuchen können. Aspekte können in XML-Form als Kataloge verwaltet und dadurch in mehreren Projekten verwendet werden.<br/>
Während der Review-Sitzung können Befunde mit PearReview in einem Protokoll notiert, verwaltet und exportiert werden. </p>
<p> <u>Nachtrag:</u> Das Projekt wurde gestern (24.07.2024) abgeschlossen und uns drängte sich die Frage auf, welche Zukunft PearReview einschlagen sollte. Daher haben wir (die Entwickler) einen einfachen Plan aus 2 Schritten ausgearbeitet, der das weitere Vorgehen bestimmen wird: </p>
<ul>
<li>Schritt 1 - Wartung und Verbreitung
<ul>
<li>Korrektur bestehender Fehler</li>
<li>Verbesserung einiger Usability-Macken</li>
<li>Verbreitung von PearReview</li>
</ul>
</li>
<li>Schritt 2 - Erweiterung
<ul>
<li>Sammeln guter Ideen</li>
<li>Erweiterung der Funktionen</li>
</ul>
</li>
</ul>
<p>
Es ist daher auch eine neue Website in Planung, die die neuen Anforderungen (Bugtracking usw.) erfüllen kann. Unser Plakat aus der gestrigen Präsentation steht ebenfalls zum <a href="PearReview-Plakat.pdf">Download</a> bereit. Wir würden uns über <a href="kontakt">Feedback</a> sehr freuen.</p>
<p></p>
<p>* PearReview unterstützt die Vorgehensweise, die in "Ludewig, J. and Lichter, H. (2008): Software Engineering. dpunkt.verlag GmbH, ISBN 3-89864-268-2" beschrieben wird. Weiterführende Links zu Reviews:</p>
<p>Deutsch:<br/>
http://de.wikipedia.org/wiki/Review_(Softwareentwicklung)<br/>
<a href="https://de.wikipedia.org/wiki/Peer-Review">http://de.wikipedia.org/wiki/Peer-Review</a></p>
<p>English:<br/>
<a href="https://en.wikipedia.org/wiki/Software_review" target="_blank">http://en.wikipedia.org/wiki/Software_review</a></p>
<p> <a href="https://en.wikipedia.org/wiki/Software_inspection" target="_blank">http://en.wikipedia.org/wiki/Software_inspection</a><br/>
<a href="https://en.wikipedia.org/wiki/Software_peer_review" target="_blank">http://en.wikipedia.org/wiki/Software_peer_review</a><br/>
<a href="https://en.wikipedia.org/wiki/Peer_review" target="_blank">http://en.wikipedia.org/wiki/Peer_review</a></p>
<p>Русский:<br/>
<a href="https://ru.wikipedia.org/wiki/%D0%A0%D0%B5%D1%86%D0%B5%D0%BD%D0%B7%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5" target="_blank">http://ru.wikipedia.org/wiki/Рецензирование</a></p>
</div>
<ul class="links inline"><li class="node_translation_en first"><a href="en/home" title="Home" class="translation-link">English</a></li>
<li class="node_translation_ru last"><a href="ru/главная" title="Главная" class="translation-link">Русский</a></li>
</ul>
</div></div> <!-- /node-inner, /node -->
</div>
</div></div> <!-- /#content-inner, /#content -->
<div id="navbar"><div id="navbar-inner" class="clear-block region region-navbar">
<a name="navigation" id="navigation"></a>
<div id="primary">
<ul class="links"><li class="menu-159 active-trail first active"><a href="startseite" title="Startseite" class="active">Startseite</a></li>
<li class="menu-191"><a href="features" title="Features">Features</a></li>
<li class="menu-188"><a href="download" title="Download">Download</a></li>
<li class="menu-180"><a href="impressum" title="Impressum">Impressum</a></li>
<li class="menu-123"><a href="kontakt" tit