Найден корректный robots.txt
Кол-во редиректов для файла robots.txt 3 слишком большое! Это может вызывать затруднение при индексации поисковыми роботами!
Проверяемая страница не запрещена в robots.txt.
Цепочка редиректов для файла robots.txt:
http://whois.uniregistry.net/robots.txt
301 MovedPermanently
https://whois.uniregistry.net/robots.txt
302 Found
https://whois.uniregistry.net/
200 OK
Показать содержимое robots.txt
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Tucows Registry</title>
<link rel="stylesheet" href="/static/css/bootstrap.css">
<link rel="stylesheet" href="/static/css/tucows/style.css">
<link rel='shortcut icon' type='image/x-icon' href='/static/images/tucows/favicon.ico' />
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Signika:wght@300;400;500;600;700&display=swap" rel="stylesheet">
</head>
<body>
<script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.2/jquery.min.js"></script>
<script type="text/javascript">window.jQuery || document.write('\x3Cscript src="/static/js/jquery-1.11.2.min.js"><\/script>')</script>
<script src="/static/js/bootstrap.min.js"></script>
<script type="text/javascript" src="/static/js/jquery.main.js"></script>
<div id="wrapper">
<header id="header" class="navbar navbar-default navbar-fixed-top" role="navigation">
<div class="container-fluid">
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#nav">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<div class="logo navbar-brand"><a href="https://www.tucowsregistry.com/" ><div class="logo-index-theme"></div></a></div>
</div>
</div>
</header>
<div class="visual win-height bg-index">
<div class="text-holder">
<div class="content-holder">
<div class="container">
<div class="row">
<div class="col-sm-10 col-sm-offset-1 lookup-text">
<h1><span class="theme-title exception">WHOIS</span> Lookup</h1>
<span class="subtext">Query our extensions</span>
<form class="form-inline lookup-form" role="form" action="/whois/" method="POST">
<div class="form-group">
<label class="sr-only" for="lookup-name">Name</label>
<input name="keyword" type="text" class="form-control input-lg" id="lookup-name" placeholder="Domain name, nameserver, registrar...">
</div>
<button type="submit" class="btn btn-default input-lg">LOOKUP</button>
</form>
</div>
</div>
</div>
</div>
</div>
<a href="#gray-panel" class="scroll-down">scroll-down</a>
</div>
<div class="gray-panel text-center" id="gray-panel">
<div class="container">
<div class="accordeon-holder" id="accordion">
<div class="panel">
<span class="accordeon-opener collapsed" data-parent="#accordion" data-toggle="collapse" data-target="#rdap-policy">RDAP API <span class="glyphicon glyphicon-chevron-up"></span><span class="glyphicon glyphicon-chevron-down"></span></span>
<div id="rdap-policy" class="collapse accordeon-drop">
<p>The API interface complies with the behavior stated in the RDAP's RFCs:</p>
<ul>
<li><a class="light-link" href="https://www.rfc-editor.org/rfc/rfc7480.txt">RFC7480</a> - HTTP Usage in the Registration Data Access Protocol (RDAP)</li>
<li><a class="light-link" href="https://www.rfc-editor.org/rfc/rfc7481.txt">RFC7481</a> - Security Services for the Registration Data Access Protocol (RDAP)</li>
<li><a class="light-link" href="https://www.rfc-editor.org/rfc/rfc7482.txt">RFC7482</a> - Registration Data Access Protocol (RDAP) Query Format</li>
<li><a class="light-link" href="https://www.rfc-editor.org/rfc/rfc7483.txt">RFC7483</a> - JSON Responses for the Registration Data Access Protocol (RDAP)</li>
<li><a class="light-link" href="https://www.rfc-editor.org/rfc/rfc7484.txt">RFC7484</a> - Finding the Authoritative Registration Data (RDAP) Service</li>
<li><a class="light-link" href="https://www.rfc-editor.org/rfc/rfc7484.txt">RFC8056</a> - Extensible Provisioning Protocol (EPP) and Registration Data Access Protocol (RDAP) Status Mapping</li>
</ul>
<p>This implementation conforms to the <a class="light-link" href="https://www.icann.org/resources/pages/rdap-operational-profile-2016-07-26-en">RDAP Operational Profile for gTLD Registries and Registrars</a> version 1.0. You can query for Domains, Nameservers, and Entities (Registrar objects). <b>Querying for Contact objects is not supported.</b></p>
<p>Queries can be done for an exact match when the resource is specified directly in the URL. For example, to query for domain names, point the RESTful client to: <code>/rdap/domain/example.com</code> where <em>example.com</em> is the TLD to query.</p>
<p>Queries can also be done using the asterisk as the wildcard character to match zero or more trailing characters. For example, a domain search by name:<code>/rdap/domains?name=exam*.com</code> will return results for the domain names exam.com, exams.com, example.com, etc.</p>
<p>The only <em>content-type</em> supported in our responses is <code>application/rdap+json</code>. If an RDAP client sends the <code>Accept</code> header in its request we will ignore it.</p>
</div>
</div>
</div>
</div>
</div>
<div class="gray-block">
<div class="container">
<div class="row">
<div class="col-md-10 col-md-offset-1">
<div class="content text-center">
<h2>Usage of our <span class="theme-title">WHOIS</span> tools</h2>
</div>
<div class="bottom-text">
<p>The WHOIS information provided in this page has been redacted in compliance with ICANN's Temporary Specification for gTLD Registration Data.</p>
<p>The data in this record is provided by Tucows Registry for informational purposes only, and it does not guarantee its accuracy. Tucows Registry is authoritative for whois information in top-level domains it operates under contract with the Internet Corporation for Assigned Names and Numbers. Whois information from other top-level domains is provided by a third-party under license to Tucows Registry.</p>
<p>This service is intended only for query-based access. By using this service, you agree that you will use any data presented only for lawful purposes and that, under no circumstances will you use (a) data acquired for the purpose of allowing, enabling, or otherwise supporting the transmission by e-mail, telephone, facsimile or other communications mechanism of mass unsolicited, commercial advertising or solicitations to entities other than your existing customers; or (b) this service to enable high volume, automated, electronic processes that send queries or data to the systems of any Registrar or any Registry except as reasonably necessary to register domain names or modify existing domain name registrations.</p>
<p>Tucows Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. All rights reserved.</p>
</div>
<div class="bottom-text">
<p>For more information on Whois status codes, please visit <a href="https://icann.org/epp">https://icann.org/epp</a></p>
<p>You can learn more about Whois by reading ICANN's educational and policy materials, available at <a href="https://whois.icann.org">https://whois.icann.org</a>.</p>
</div>
</div>
</div>
</div>
</div>
<footer id="footer">
<div class="footer-content">
<div class="container">
<div class="row">
<div class="col-lg-10 col-lg-offset-1">
<div class="row">
<div class="col-md-3 col-sm-12">
</div>
</div>
</div>
</div>
</div>
</div>
<div class="subscribe-panel text-center">
<div class="container">
</div>
</div>
<div class="footer-bottom">
<div class="container-fluid">
<div class="footer-section">
<div class="footer-section-copyright">
Copyright © 2026 - Tucows Registry. All rights reserved
</div>
<div class="footer-section-powered">
<img class="footer-brand-logo" src="/static/images/powered-by-tucows-white.svg" />
</div>
</div>
</div>
</div>
</footer>
</div>
</body>
</html>
