Report for kemono.party (2024)

NS Records at Parent Servers

Missing Glue

Test ignored, name servers are located outside of current zone.

Name Servers Have A Records

Name Servers Have AAAA Records

NS Records

All Name Servers Responded

OK. All your name servers responded. We queried domain's records from all of your name servers and we received them successfully.

Glue Check

OK. No differences found. The glue provided by the parent name servers has to matchthe data provided by the authoritative name servers.

Allow Recursive Queries

OK. Domain name servers are not allowing recursive queries. On all name servers which acts as caching name servers recursive queries should be restricted to local networks.Having open DNS servers can lead to abuses such as cache poisoning and DOS (denial of service) attacks.Cache poisoning attacks allows under certain conditions to redirect legitimate web traffic,email and other traffic to malicious hosts compromising security.

Check Name Servers Count

OK. Domain has 3 name servers. Recommended number,between 2 and 7 name servers (RFC 2182 recommends to have atleast 3 authoritative name servers for domains).

Identical NS Records

OK. All your name servers reported identical NS records. Each name server should return identical NS records.

Check for Lame Name servers

OK. No lame name servers found. All of your name servers are configured to be either master or slave for your domain.

Check All IPs are Public

OK. No private IPs found. Name servers using private IPs can't be reached from the Internet causing DNS delays.

Name Servers Have A Records

Name Servers Have AAAA Records

Name Servers Have Valid Names

OK. All names are valid. Name server name should be a valid host name, no partial name or IP address.

Check for Stealth Name Servers

OK. No stealth name servers found. All name servers returned by domain name servers should be listed at parent servers.

Check for Missing Name Servers

OK. No missing name servers found. All name servers returned by the parent name servers should have an NS record at your name servers.

No CNAME in NS Records

OK. No CNAMEs found in NS records. RFC 2181, section 10.3 says that host name must map directly to one or more address record (A or AAAA)and must not point to any CNAME records.RFC 1034, section 3.6.2 says if a name appears in the right-hand side of RR (Resource Record)it should not appear in the left-hand name of CNAME RR, thus CNAME records should not be used withNS and MX records.Despite this restrictions, there are many working configuration using CNAME withNS and MX records.

Allow TCP connections

OK. All name servers are allowing TCP connections. When response to a DNS query exceeds 512 bytes, TCP is negotiated and used, all name servers should allow TCP connections (port 53).

Name Servers Distributed on Multiple Networks

Name Servers Distributed on Multiple ASNs

Name Servers Versions

Check SOA Record

Name Servers Agreement on Serial Number

OK. All name servers (3) have the same serial number [2024072502]. Having different serials on your name servers may show inconsistencies between name serversconfiguration (multiple masters), or communication errors (ACL and firewall issues).

SOA Number Format

OK. Serial number format OK [2024072502]. Your serial number is following general convention for serial number YYYYMMDDnn, where YYYY is four-digit year number, MM is the month, DD is the day and nn is the sequence number in case zone file is updated more than once per day.

SOA Mname

OK. Primary name server is ns1.kemono.ru. and is listed at the parent name servers. The MNAME field defines the Primary Master name server for the zone, this name server should be found in your NS records.

SOA Rname

OK. Contact email for DNS problems is [emailprotected]. (soa.kemono.ru.). RNAME field defines an administrative email for your zone. RFC2142 recommends using hostmaster e-mail for this purpose, but any valid e-mail address can be used.

SOA Refresh

OK. Refresh interval is 14400. Recommended values [1200 .. 43200] (20 min ... 12 hours).Refresh field from SOA record determines how quickly zone changes are propagated from master to slave.

SOA Retry

OK. Retry interval is 3600. Recommended values [120 .. 7200] (2 minutes .. 2 hours).Retry field from SOA record defines how often slave should retry contacting master if connection to master failed during refresh.

SOA Expire

OK. Expire interval is 1209600. Recommended values [604800 .. 1209600] (1 week ... 2 weeks).Expiry defines zone expiration time in seconds after which slave must re-validate zone file,if contacting master fails then slave will stop responding to any queries.

SOA Minimum TTL

OK. Minimum TTL value is 86400. Recommended values [3600 .. 86400] (1 hour ... 1 day).Minimum TTL was redefined in RFC 2308, now it defines the period of time used by slavesto cache negative responses.

MX Records

Identical MX Records

OK. All name servers returned identical MX records.

Mail Servers Have A Records

Mail Servers Have AAAA Records

Reverse Entries for MX records

Check MX Records for Invalid Chars

OK. No invalid characters found. Name field from MX records should be a valid host name.

Check MX Records IPs are Public

OK. No private IPs found. Mail servers using private IPs can't be reached from the Internet causing mail delivery delays.

Check MX Records for Duplicates

OK. No MX records duplicates (same IP addresses) found. Although technically valid, duplicate MX records have no benefits and can cause confusion.

Only Host Names in MX Records

OK. No IPs found in MX records. IP addresses are not allowed in MX records, only host names.

No CNAME in MX Records

OK. No CNAMEs found in MX records. RFC 2181, section 10.3 says that host name must map directly to one or more address record (A or AAAA)and must not point to any CNAME records.RFC 1034, section 3.6.2 says if a name appears in the right-hand side of RR (Resource Record)it should not appear in the left-hand name of CNAME RR, thus CNAME records should not be used withNS and MX records.Despite this restrictions, there are many working configuration using CNAME withNS and MX records.

RBL Check

OK. Mail servers IPs are not blacklisted.

Check Google Apps Settings

Test ignored, domain is not using Google Apps.

Connect to Mail Servers

Could not get MX records from your name servers.

Resolve Domain Name

Domain Name IPs are Public

OK. No private IPs found for kemono.party.. Web servers using private IPs can't be reached from the Internet.

Resolve WWW

WWW IPs are Public

OK. No private IPs found for www.kemono.party.. Web servers using private IPs can't be reached from the Internet.