Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSFIX
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
HTTP version does not redirect to HTTPS
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNS Records2 A records, 40 ms lookupREVIEW
| A | 119.188.211.99, 49.74.197.110 |
| AAAA | — |
| CNAME | renren.com.eo.dnse0.com |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
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)
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
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.
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.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>人人网</title>
<style>
html,body {
height: 100%;
width: 100%;
margin: 0;
padding: 0;
}
body {
position: relative;
}
.img{
width: 100%;
height: 100%;
background: url('./img/background.png') no-repeat;
overflow: hidden;
position: absolute;
z-index: 1;
top: 0;
left: 0;
}
.box{
width: 100%;
height: 100%;
position: relative;
z-index: 100;
}
.pc{
width: 100%;
height: 100%;
display: flex;
justify-content: center;
align-items: center;
flex-flow: column;
}
.h5{
display: none;
}
.pc-img{
width: 100%;
height: calc(100% - 100px);
overflow: hidden;
}
.pc-img img{
max-width: 100%;
}
.text {
font-size: 12px;
display: flex;
align-items: center;
justify-content: center;
flex-flow: column;
height: 100px;
color: hsl(0deg 0% 100% / 50%);
}
.text a{
color: hsl(0deg 0% 100% / 50%);
}
.a1 {
display: flex;
margin-top: 2px;
}
.a2 {
margin-right: 20px;
}
.a3 {
margin-right: 10px;
}
.a4 {
justify-content: space-between;
min-width: 400px;
}
@media screen and (max-width: 500px) {
.img{
overflow: hidden;
position: absolute;
z-index: 1;
top: 0;
left: 0;
}
.pc{
display: none;
}
.h5{
display: block;
position: relative;
height: 100%;
width: 100%;
display: flex;
justify-content: center;
align-items: center;
flex-flow: column;
}
.container{
position: absolute;
bottom: 109px;
width: calc(90%);
margin: 0 auto;
height: calc(100% - 120px);
display: flex;
justify-content: center;
align-items: center;
}
.container .content{
background: #fff;
border-radius: 8px;
padding: 10px 20px;
display: flex;
justify-content: center;
flex-flow: column;
}
.container .content img{
max-width: 80px;
}
.container .content p{
font-size: 14px;
margin: 0;
margin-top: 13px;
}
.icp{
width: calc(90%);
margin: 0 auto;
font-size: 12px;
color: hsl(0deg 0% 100% / 50%);
position: absolute;
bottom: 20px;
padding: 10px 0;
}
.icp p{
margin: 0;
}
.icp a{
color: hsl(0deg 0% 100% / 50%);
}
.h5-a1{
display: flex;
justify-content: center;
margin-top: 3px;
}
.h5-a1 div{
width: 50%;
}
.h5-a2{
margin-top: 3px;
display: flex;
}
.h5-a3{
justify-content: space-between;
}
.h5-a4{
display: flex;
margin-top: 3px;
}
}
</style>
</head>
<body>
<div class="img"></div>
<div class="box">
<div class="pc">
<div class="pc-img">
<img src="./img/notice2.png" alt="">
</div>
<div class="text">
<div class="a1">
<div class="a2">公司全称：成都人人互娱科技有限公司 </div>
</div>
<div class="a1 a4">
<div>违法信息不良举报电话：010-87538607</div>
<div>邮箱：jubao@infinities.com.cn</div>
</div>
<div class="a1">
<a class="a3" href="https://beian.miit.gov.cn/" target="_blank" data-v-ae6a3fd4="">蜀ICP备2021009929号-11</a>
</div>
<div>人人网©2025</div>
</div>
</div>
<div class="h5">
<div class="container">
<div class="content">
<img src="./img/header.png" alt="人人网"/>
<p style="font-weight: bold;font-size: 16px;margin-top: 20px;">人人网服务升级公告</p>
<p>亲爱的人人网用户们，</p>
<p>感谢您一直以来的陪伴与支持!我们想告诉您，人人网正在进行一次“换车”升级--就像您的燃油车开了多年，也想试试新能源车一样。</p>
<p>在这期间，您在人人网上的所有数据都得到了严格的保护，确保您的个人信息和隐私安全不受任何威胁。您的数据安全，对我们来说至关重要。</p>
<p>请耐心等待我们的“新车”上路，届时您将享受到更加稳定安全、丰富的社交体验，让我们共同期待人人网的全新启程!</p>
<p>此致!</p>
<p style="margin-bottom: 0;font-weight: bold;">人人网团队</p>
<p style="margin: 0;font-weight: bold;">2024年12月2日</p>
</div>
</div>
<div class="icp">
<div class="h5-a1">公司全称：成都人人互娱科技有限公司</div>
<div class="h5-a1">违法信息不良举报电话：010-87538607</div>
<div class="h5-a1">邮箱：jubao@infinities.com.cn</div>
<div class="h5-a1">
<div><a href="https://beian.miit.gov.cn/" target="_blank" data-v-ae6a3fd4="">蜀ICP备2021009929号-11</a></div>
</div>
<div class="h5-a1">人人网©2025</div>
</div>
</div>
</div>
</body>
</html>
BHTTP Probe TimingTotal 947 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations258 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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+Redirect ChainNo redirects — direct accessPASS
https://renren.com
653 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://renren.com | 200 | 653 ms | HTTP/1.1 | nginx |
A+Domain Intelligencerenren.com — via DNSPod, Inc., 27 years, 6 months old, hosted on CHINA169-BACKBONE CHINA UNICOM China169 Backbone, CNPASS
198 days
March 3, 2027
258 days
Issued by WoTrus CA Limited
27 years, 6 months
Registered March 3, 1999
Not enabled
Protects against DNS spoofing
CHINA169-BACKBONE CHINA UNICOM China169 Backbone, CN
ASN AS4837
119.188.211.99
DNSPod, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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