DNS report
kuzbashimbank.ru
Complete DNS, mail, web and security analysis.
DNS cache tools
If you have recently made DNS changes and they are not yet reflected in the report, you can try to flush the DNS cache of these public resolvers: The domain name will be copied to your clipboard automatically when clicking on a button
| Category | Status | Test | Details | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Warning | Delegated nameservers are not responding |
Public resolvers return DNS records for this domain, but direct queries to the authoritative servers fail from DNSprobe. The report displays public resolver data. This failure does not prove that the DNS zone is missing; some direct checks remain unavailable.
How can you fix this?
|
|||||||||||||||||||||||||||||||||||||
|
WHOIS0.0 ms |
Domain Status |
Unable to retrieve WHOIS information for kuzbashimbank.ru.
Retry, this time it might work! Reason: empty whois/rdap response |
|||||||||||||||||||||||||||||||||||||
|
PARENT0.0 ms |
Domain NS records |
Nameserver records returned by the parent servers are:
ns1.reg.ru [194.58.117.17, 176.99.13.11, 176.99.13.13, 176.99.13.15, 176.99.13.17, 194.58.117.11, 194.58.117.13, 194.58.117.15, 2a00:f940:9::1:1, 2a00:f940:9::2:1] (NO GLUE) [TTL=86400] ns2.reg.ru [176.99.13.12, 176.99.13.14, 176.99.13.16, 176.99.13.18, 194.58.117.12, 194.58.117.14, 194.58.117.16, 194.58.117.18, 2a00:f940:9::1:2, 2a00:f940:9::2:2] (NO GLUE) [TTL=86400] Information obtained via fallback resolver 1.1.1.1 because the TLD server e.dns.ripn.net did not return NS records. |
|||||||||||||||||||||||||||||||||||||
| TLD Parent Check |
The parent server did not return any information for this TLD.
|
||||||||||||||||||||||||||||||||||||||
| Your nameservers are listed |
e.dns.ripn.net has your nameservers listed.
This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers. |
||||||||||||||||||||||||||||||||||||||
| DNS Parent sent Glue |
0 of 2 nameservers sent GLUE.
The parent nameserver a.gtld-servers.net is not sending out GLUE for every nameserver listed, meaning it is sending your nameserver hostnames without their corresponding A records. This is acceptable, but it requires an extra A record lookup, which may slightly delay DNS resolution. This often occurs when nameservers are on a different TLD (e.g., domain.com with nameserver ns.otherdomain.com). |
||||||||||||||||||||||||||||||||||||||
| Nameservers A records |
Every nameserver listed has A records.
This is a must if you want to be found. |
||||||||||||||||||||||||||||||||||||||
|
NS11358.4 ms |
NS records from your NameServers |
NS records returned by the currently delegated nameservers are:
Oops! I could not get any nameservers from your nameservers. Please verify that the nameservers listed at the parent are not lame and are configured properly. Nameservers with no NS response: ns1.reg.ru ns2.reg.ru |
|||||||||||||||||||||||||||||||||||||
| Public Resolver |
|
||||||||||||||||||||||||||||||||||||||
| Mismatched NS records |
The NS records at all your nameservers are identical to those listed by the parent.
WARNING: One or more of your nameservers did not return any of your NS records. |
||||||||||||||||||||||||||||||||||||||
| DNS servers responded |
The following NS did not respond to a basic query:
ns1.reg.ru ns2.reg.ru ❌ These nameservers did not respond to a standard non-recursive A query. This may indicate filtering, timeouts, or misconfiguration. |
||||||||||||||||||||||||||||||||||||||
| Name of nameservers are valid |
All of the NS records that your nameservers report seem valid.
|
||||||||||||||||||||||||||||||||||||||
| Multiple Nameservers |
You have 2 nameservers. This is acceptable, but having 3 or more is recommended according to RFC2182 section 5.
Having 2 nameservers is ok by me. |
||||||||||||||||||||||||||||||||||||||
| Missing nameservers reported by parent |
All NS records are the same at the parent and at your nameservers.
|
||||||||||||||||||||||||||||||||||||||
| Missing nameservers reported by your nameservers |
All nameservers returned by the parent server are the same as the ones reported by your nameservers.
|
||||||||||||||||||||||||||||||||||||||
| Domain CNAMEs |
OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
|
||||||||||||||||||||||||||||||||||||||
| NSs CNAME check |
OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
|
||||||||||||||||||||||||||||||||||||||
| Different subnets |
All nameservers are on the same subnet (can be a risk).
|
||||||||||||||||||||||||||||||||||||||
| Recursive Queries |
ns1.reg.ru → ❌ This DNS server allows recursion, which may pose a security risk (it responds to out-of-zone queries).
ns2.reg.ru → ❌ This DNS server allows recursion, which may pose a security risk (it responds to out-of-zone queries). |
||||||||||||||||||||||||||||||||||||||
| Same Glue |
I do not consider this an error because no authoritative nameserver returned NS records for this domain.
|
||||||||||||||||||||||||||||||||||||||
| NS Self-IP Consistency |
Test skipped because no authoritative nameserver responded well enough to perform this check.
|
||||||||||||||||||||||||||||||||||||||
| Glue for NS records |
The delegated nameservers did not return NS records for this domain, so DNSprobe cannot verify child-side glue. This is treated as a pass because the main delegation problem has already been reported.
|
||||||||||||||||||||||||||||||||||||||
| Nameservers are lame |
OK. The nameservers listed at the parent are the delegated nameservers for this domain. No additional lame nameserver condition was detected beyond the response issue already reported above.
|
||||||||||||||||||||||||||||||||||||||
| IPs of nameservers are public |
Ok. Looks like the IP addresses of your nameservers are public.
This is a good thing because it will prevent DNS delays and other problems. |
||||||||||||||||||||||||||||||||||||||
| DNS servers allow TCP connection |
Some authoritative name servers do not respond over TCP:
ns1.reg.ru (194.58.117.11) ns2.reg.ru (194.58.117.16) TCP support is important for large DNS replies (DNSSEC, long responses, truncation fallback). |
||||||||||||||||||||||||||||||||||||||
| Different autonomous systems |
All authoritative name servers appear to be in the same autonomous system: AS197695.
Using a single AS reduces resiliency and increases the blast radius of network incidents. Consider hosting your NS records across multiple autonomous systems. WARNING: Single point of failure. |
||||||||||||||||||||||||||||||||||||||
| Stealth NS records sent |
Ok. No stealth NS records are sent
|
||||||||||||||||||||||||||||||||||||||
|
DNSSEC935.1 ms |
Zone signed |
DNSSEC: Unsigned
No RRSIG record found. The zone is not signed with DNSSEC. |
|||||||||||||||||||||||||||||||||||||
| DNSKEY records |
No DNSKEY records found.
|
||||||||||||||||||||||||||||||||||||||
| DS record in parent |
No DS record found in the parent zone.
|
||||||||||||||||||||||||||||||||||||||
| NSEC/NSEC3 record |
No NSEC or NSEC3 record found when querying a non-existent subdomain.
This may indicate a misconfiguration or lack of proper DNSSEC denial-of-existence support. |
||||||||||||||||||||||||||||||||||||||
|
SOA0.1 ms |
SOA Record |
The SOA (Start of Authority) record is:
Primary nameserver: ns1.reg.ru Hostmaster E-mail address: hostmaster@ns1@reg@ru Serial #: 1788942064 Refresh: 14400 Retry: 3600 Expire: 604800 Default TTL: 10800 |
|||||||||||||||||||||||||||||||||||||
| NSs have same SOA serial |
Comparison unavailable: DNSprobe did not obtain a usable response from every authoritative server. Public resolver data cannot confirm their consistency.
|
||||||||||||||||||||||||||||||||||||||
| SOA MNAME entry |
OK. ns1.reg.ru is listed at the parent servers.
|
||||||||||||||||||||||||||||||||||||||
| SOA Serial |
Your SOA serial number is: 1788942064. This appears to follow the recommended YYYYMMDDnn format.
|
||||||||||||||||||||||||||||||||||||||
| SOA REFRESH |
Your SOA REFRESH interval is: 14400. OK.
|
||||||||||||||||||||||||||||||||||||||
| SOA RETRY |
Your SOA RETRY value is: 3600. OK.
|
||||||||||||||||||||||||||||||||||||||
| SOA EXPIRE |
Your SOA EXPIRE number is: 604800. Looks OK.
|
||||||||||||||||||||||||||||||||||||||
| SOA MINIMUM TTL |
Your SOA MINIMUM TTL is: 10800. This is fine
|
||||||||||||||||||||||||||||||||||||||
|
MX ... |
MX Records |
|
|||||||||||||||||||||||||||||||||||||
|
TXT0.1 ms |
TXT Records |
|
|||||||||||||||||||||||||||||||||||||
|
SPF ... |
SPF Analysis |
|
|||||||||||||||||||||||||||||||||||||
|
DMARC149.6 ms |
DMARC Configuration |
DMARC Record was found:
v=DMARC1; p=none; rua=mailto:[email protected] Policy summary:
v=DMARC1; p=none; sp=none; rua=mailto:[email protected]; ruf=none; fo=0; pct=100; adkim=r; aspf=r; ri=86400; rf=afrf; DMARC Evaluation Score: 1/3 To improve your score:
|
|||||||||||||||||||||||||||||||||||||
|
MTA-STS / TLS-RPT748.5 ms |
Mail TLS security |
MTA-STS score 0/5 Recommendations:
|
|||||||||||||||||||||||||||||||||||||
|
DKIM ... |
DKIM Records Detected |
|
|||||||||||||||||||||||||||||||||||||
|
BIMI267.6 ms |
BIMI Record |
No BIMI record found at: default._bimi.kuzbashimbank.ru.
|
|||||||||||||||||||||||||||||||||||||
|
SSL ... |
SSL Certificate Summary |
|
|||||||||||||||||||||||||||||||||||||
|
CAA ... |
CAA Records |
|
|||||||||||||||||||||||||||||||||||||
|
HSTS ... |
HSTS |
|
|||||||||||||||||||||||||||||||||||||
|
HTTPS ... |
HTTPS |
|
|||||||||||||||||||||||||||||||||||||
|
HTTPS (DNS) ... |
HTTPS DNS record |
|
|||||||||||||||||||||||||||||||||||||
|
WWW ... |
A Record |
|
|||||||||||||||||||||||||||||||||||||
|
AXFR (Zone Transfer)16029.2 ms |
AXFR status for the zone |
AXFR test could not be determined for kuzbashimbank.ru.
Nameservers tested: ns1.reg.ru, ns2.reg.ru |
|||||||||||||||||||||||||||||||||||||
| Security note |
Zone transfers (AXFR) should be disabled in production unless explicitly required and restricted.
Leaving AXFR open allows anyone to enumerate your entire DNS zone (subdomains, MX, TXT, internal hosts, etc.). |
||||||||||||||||||||||||||||||||||||||
|
PORTS ... |
Open ports detected (80.250.211.30) |
|
|||||||||||||||||||||||||||||||||||||
|
REPUTATION ... |
IP in blacklists (80.250.211.30) |
|
|||||||||||||||||||||||||||||||||||||
|
DNS found ... |
|
||||||||||||||||||||||||||||||||||||||
| Test | Details | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Website Preview0.0 ms
|
Snapshot is generated through DNSprobe's rendering proxy and may be served from a short cache.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Security Headers20012.1 ms
|
Score: 5/100 (F) Failing, very weak or absent security headers
Recommended starter configuration (.htaccess) Starter configuration to copy and adapt. CSP, CORS and cookie rewriting are intentionally commented because they can break some sites if enabled blindly. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| WHOIS |
Unable to retrieve registration data for kuzbashimbank.ru.
|
Processed in 0.009 seconds.
Made with with PHP and a bit of JS.
Made with with PHP and a bit of JS.
Lines of code: 20,304