Check DNS, Urls + Redirects, Certificates and Content of your Website



X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
23.06.2022 11:35:56


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
bounce.mindbox.ru
A
130.193.36.220
Moscow/Russia (RU) - Yandex enterprise network
No Hostname found
yes
1
0

AAAA

yes


www.bounce.mindbox.ru

Name Error
yes
1
0
*.mindbox.ru
A

yes



AAAA

yes



CNAME
mindbox-cdp.trafficmanager.net
yes


*.bounce.mindbox.ru
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



Status: Valid because published



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 20826, Flags 256



Public Key with Algorithm 8, KeyTag 47671, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.07.2022, 00:00:00 +, Signature-Inception: 20.06.2022, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: ru
ru
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 33257, DigestType 2 and Digest ZBoLoCehAn0v0XtXQ5MYBO67MpuLUUo1fR7ykPFZ158=



1 RRSIG RR to validate DS RR found



RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 06.07.2022, 05:00:00 +, Signature-Inception: 23.06.2022, 04:00:00 +, KeyTag 47671, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 47671 used to validate the DS RRSet in the parent zone



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 33257, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 53436, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 345600 sec, Signature-expiration: 07.07.2022, 00:00:00 +, Signature-Inception: 17.06.2022, 00:00:00 +, KeyTag 33257, Signer-Name: ru



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 33257 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 33257, DigestType 2 and Digest "ZBoLoCehAn0v0XtXQ5MYBO67MpuLUUo1fR7ykPFZ158=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: mindbox.ru
mindbox.ru
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "5irtdr9nl8d19lelt95daiob4tk6foe5" between the hashed NSEC3-owner "5irsa7dq741knp7nsd6afv0v5la6l5hh" and the hashed NextOwner "5jh7v8noh1tusvkkh9s1gtvlvql4g4ka". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 5irsa7dq741knp7nsd6afv0v5la6l5hh.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 10.07.2022, 02:11:56 +, Signature-Inception: 28.05.2022, 14:19:04 +, KeyTag 53436, Signer-Name: ru



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "tdui9d4jkuds8b9t86gj39pgflcnlgm5" as Owner. That's the Hash of "ru" with the NextHashedOwnerName "te33kgtaqu9m5crq3ibsilqu11gfgttt". So that domain name is the Closest Encloser of "mindbox.ru". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner tdui9d4jkuds8b9t86gj39pgflcnlgm5.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 07.07.2022, 13:27:33 +, Signature-Inception: 30.05.2022, 20:44:06 +, KeyTag 53436, Signer-Name: ru



0 DNSKEY RR found




Zone: bounce.mindbox.ru
bounce.mindbox.ru
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.bounce.mindbox.ru
www.bounce.mindbox.ru
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.bounce.mindbox.ru
  ns1-04.azure-dns.com

bounce.mindbox.ru
  ns1.yandexcloud.net
2a0d:d6c1:0:1a::1b4
Moscow/Russia (RU) - Yandex.Cloud LLC


  ns1-04.azure-dns.com
2603:1061::4
Ashburn/Virginia/United States (US) - Microsoft Corporation

mindbox.ru
  ns1.yandexcloud.net
2a0d:d6c1:0:1a::1b4
Moscow/Russia (RU) - Yandex.Cloud LLC


  ns1-04.azure-dns.com
2603:1061::4
Ashburn/Virginia/United States (US) - Microsoft Corporation


  ns2.yandexcloud.net
2a0d:d6c1:0:1a::2c9
Moscow/Russia (RU) - Yandex.Cloud LLC


  ns2-04.azure-dns.net
2620:1ec:8ec::4
Toronto/Ontario/Canada (CA) - Microsoft Corporation


  ns3-04.azure-dns.org
2a01:111:4000::4
Dublin/Leinster/Ireland (IE) - Microsoft Corporation


  ns4-04.azure-dns.info
2620:1ec:bda::4
Toronto/Ontario/Canada (CA) - Microsoft Corporation

ru
  a.dns.ripn.net


  b.dns.ripn.net


  d.dns.ripn.net / tau-lax.ripn.net


  e.dns.ripn.net / gamma-ekt.ripn.net


  f.dns.ripn.net


4. SOA-Entries


Domain:ru
Zone-Name:ru
Primary:a.dns.ripn.net
Mail:hostmaster.ripn.net
Serial:4051822
Refresh:86400
Retry:14400
Expire:2592000
TTL:3600
num Entries:5


Domain:mindbox.ru
Zone-Name:mindbox.ru
Primary:ns1.yandexcloud.net
Mail:mx.cloud.yandex.net
Serial:1
Refresh:10800
Retry:900
Expire:604800
TTL:86400
num Entries:2


Domain:mindbox.ru
Zone-Name:mindbox.ru
Primary:ns1-04.azure-dns.com
Mail:azuredns-hostmaster.microsoft.com
Serial:1492428764
Refresh:10800
Retry:3600
Expire:604800
TTL:10800
num Entries:4


Domain:bounce.mindbox.ru
Zone-Name:mindbox.ru
Primary:ns1.yandexcloud.net
Mail:mx.cloud.yandex.net
Serial:1
Refresh:10800
Retry:900
Expire:604800
TTL:86400
num Entries:1


Domain:bounce.mindbox.ru
Zone-Name:mindbox.ru
Primary:ns1-04.azure-dns.com
Mail:azuredns-hostmaster.microsoft.com
Serial:1492428764
Refresh:10800
Retry:3600
Expire:604800
TTL:10800
num Entries:1


Domain:www.bounce.mindbox.ru
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

DomainnameHttp-StatusredirectSec.G
• http://bounce.mindbox.ru/
130.193.36.220
-14

10.040
T
Timeout - The operation has timed out

• https://bounce.mindbox.ru/
130.193.36.220
-14

10.030
T
Timeout - The operation has timed out

• http://bounce.mindbox.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
130.193.36.220
-14

10.037
T
Timeout - The operation has timed out
Visible Content:

• https://130.193.36.220/
130.193.36.220
-14

10.047
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "bounce.mindbox.ru" is subdomain, public suffix is ".ru", top-level-domain is ".ru", top-level-domain-type is "country-code", Country is Russian Federation (the), tld-manager is "Coordination Center for TLD RU", num .ru-domains preloaded: 1928 (complete: 175327)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: bounce.mindbox.ru has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: bounce.mindbox.ru has no ipv6 address.
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain bounce.mindbox.ru, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 22 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 6 Name Servers.
AInfo:: 22 Queries complete, 22 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1-04.azure-dns.com (2603:1061::4, 40.90.4.4), ns2-04.azure-dns.net (2620:1ec:8ec::4, 64.4.48.4), ns3-04.azure-dns.org (13.107.24.4, 2a01:111:4000::4), ns4-04.azure-dns.info (13.107.160.4, 2620:1ec:bda::4)
Ok (4 - 8):: An average of 3.7 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 6 different Name Servers found: ns1.yandexcloud.net, ns1-04.azure-dns.com, ns2.yandexcloud.net, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info, 6 Name Servers included in Delegation: ns1-04.azure-dns.com, ns1.yandexcloud.net, ns2-04.azure-dns.net, ns2.yandexcloud.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info, 6 Name Servers included in 2 Zone definitions: ns1.yandexcloud.net, ns2.yandexcloud.net, ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info, 2 Name Servers listed in SOA.Primary: ns1.yandexcloud.net, ns1-04.azure-dns.com.
Error: Different SOA.Primary Name Servers found, different SOA Definitions.: ns1.yandexcloud.net,ns1-04.azure-dns.com.
Error: SOA.Primary Name Server not included in the delegation set.: ns1.yandexcloud.net,ns1-04.azure-dns.com.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns1.yandexcloud.net (2a0d:d6c1:0:1a::1b4): Delegation: ns1-04.azure-dns.com, ns1.yandexcloud.net, ns2-04.azure-dns.net, ns2.yandexcloud.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info, Zone: ns1.yandexcloud.net, ns2.yandexcloud.net. Name Servers defined in Delegation, missing in Zone: ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns1-04.azure-dns.com (2603:1061::4): Delegation: ns1-04.azure-dns.com, ns1.yandexcloud.net, ns2-04.azure-dns.net, ns2.yandexcloud.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info, Zone: ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info. Name Servers defined in Delegation, missing in Zone: ns1.yandexcloud.net, ns2.yandexcloud.net.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns2.yandexcloud.net (2a0d:d6c1:0:1a::2c9): Delegation: ns1-04.azure-dns.com, ns1.yandexcloud.net, ns2-04.azure-dns.net, ns2.yandexcloud.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info, Zone: ns1.yandexcloud.net, ns2.yandexcloud.net. Name Servers defined in Delegation, missing in Zone: ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns2-04.azure-dns.net (2620:1ec:8ec::4): Delegation: ns1-04.azure-dns.com, ns1.yandexcloud.net, ns2-04.azure-dns.net, ns2.yandexcloud.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info, Zone: ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info. Name Servers defined in Delegation, missing in Zone: ns1.yandexcloud.net, ns2.yandexcloud.net.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns3-04.azure-dns.org (2a01:111:4000::4): Delegation: ns1-04.azure-dns.com, ns1.yandexcloud.net, ns2-04.azure-dns.net, ns2.yandexcloud.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info, Zone: ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info. Name Servers defined in Delegation, missing in Zone: ns1.yandexcloud.net, ns2.yandexcloud.net.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns4-04.azure-dns.info (2620:1ec:bda::4): Delegation: ns1-04.azure-dns.com, ns1.yandexcloud.net, ns2-04.azure-dns.net, ns2.yandexcloud.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info, Zone: ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info. Name Servers defined in Delegation, missing in Zone: ns1.yandexcloud.net, ns2.yandexcloud.net.
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 6 different Name Servers found
AGood: Name servers with different Top Level Domains / Public Suffix List entries found: 6 Name Servers, 5 Top Level Domains: com, org, net, info, yandexcloud.net
AGood: Name Servers with different domain names found.: 5 different Domains found
AGood: Name servers with different Country locations found: 6 Name Servers, 4 Countries: CA, IE, RU, US
A
AInfo: IPv6-Subnet-list: 6 Name Servers with IPv6, 4 different subnets (first block): 2603:, 2620:, 2a01:, 2a0d:, 4 different subnets (first two blocks): 2603:1061:, 2620:01ec:, 2a01:0111:, 2a0d:d6c1:, 5 different subnets (first three blocks): 2603:1061:0000:, 2620:01ec:08ec:, 2620:01ec:0bda:, 2a01:0111:4000:, 2a0d:d6c1:0000:, 5 different subnets (first four blocks): 2603:1061:0000:0000:, 2620:01ec:08ec:0000:, 2620:01ec:0bda:0000:, 2a01:0111:4000:0000:, 2a0d:d6c1:0000:001a:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AInfo: Nameserver mit different domain names found. May be a problem with DNS-Updates
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1-04.azure-dns.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
XFatal error: Nameservers with different SOA Serial Numbers
Agood: CAA entries found, creating certificate is limited: globalsign.com is allowed to create certificates
Agood: CAA entries found, creating certificate is limited: godaddy.com is allowed to create certificates
Agood: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates

3. Content- and Performance-critical Checks

http://bounce.mindbox.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 130.193.36.220
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AInfo: No img element found, no alt attribute checked
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 155307 milliseconds, 155.307 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - CT-Log entries found


2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 2019 are listed

Issuerlast 7 daysactivenum Certs
CN=Thawte RSA CA 2018, OU=www.digicert.com, O=DigiCert Inc, C=US
0
0
3
CN=R3, O=Let's Encrypt, C=US
0 /0 new
1
2
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
0
1
1
CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
0
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
6720220517
precert
CN=R3, O=Let's Encrypt, C=US
2022-05-13 05:38:57
2022-08-11 05:38:56
*.mindbox.ru, mindbox.ru
2 entries


6385213179
precert
CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
2022-03-21 12:17:26
2023-04-22 11:17:25
*.mindbox.ru, autodiscover.mindbox.ru, mail.mindbox.ru, mindbox.ru, owa.mindbox.ru
5 entries


6354324165
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-03-16 16:00:14
2022-06-14 15:00:13
*.mindbox.ru, mindbox.ru
2 entries


6354003169
precert
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
2022-03-16 15:46:52
2023-04-17 14:46:52
*.mindbox.ru, mindbox.ru
2 entries


4279207327
leaf cert
CN=Thawte RSA CA 2018, OU=www.digicert.com, O=DigiCert Inc, C=US
2021-03-15 23:00:00
2022-03-21 22:59:59
*.mindbox.ru, mindbox.ru
2 entries


2481748850
leaf cert
CN=Thawte RSA CA 2018, OU=www.digicert.com, O=DigiCert Inc, C=US
2020-02-09 23:00:00
2021-04-10 10:00:00
*.mindbox.ru, mindbox.ru
2 entries


349769641
leaf cert
CN=Thawte RSA CA 2018, OU=www.digicert.com, O=DigiCert Inc, C=US
2018-02-26 23:00:00
2020-02-27 11:00:00
*.mindbox.ru, mindbox.ru
2 entries



11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.yandexcloud.net, ns1-04.azure-dns.com, ns2.yandexcloud.net, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info

QNr.DomainTypeNS used
1
net
NS
a.root-servers.net (2001:503:ba3e::2:30)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
ns1.yandexcloud.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns3.yandex.ru, ns4.yandex.ru
3
com
NS
k.root-servers.net (2001:7fd::1)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
4
ns1-04.azure-dns.com: 2603:1061::4, 40.90.4.4
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1-01.azure-dns.com
2603:1061::1, 40.90.4.1

Answer: ns1-02.azure-dns.com
2603:1061::2, 40.90.4.2

Answer: ns1-03.azure-dns.com
2603:1061::3, 40.90.4.3
5
ns2.yandexcloud.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns3.yandex.ru, ns4.yandex.ru
6
ns2-04.azure-dns.net: 2620:1ec:8ec::4, 64.4.48.4
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns2-01.azure-dns.net
2620:1ec:8ec::1, 64.4.48.1

Answer: ns2-02.azure-dns.net
2620:1ec:8ec::2, 64.4.48.2

Answer: ns2-03.azure-dns.net
2620:1ec:8ec::3, 64.4.48.3
7
org
NS
l.root-servers.net (2001:500:9f::42)

Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
8
ns3-04.azure-dns.org: 13.107.24.4, 2a01:111:4000::4
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns3-01.azure-dns.org
13.107.24.1, 2a01:111:4000::1

Answer: ns3-02.azure-dns.org
13.107.24.2, 2a01:111:4000::2

Answer: ns3-03.azure-dns.org
13.107.24.3, 2a01:111:4000::3
9
info
NS
d.root-servers.net (2001:500:2d::d)

Answer: a0.info.afilias-nst.info, a2.info.afilias-nst.info, b0.info.afilias-nst.org, b2.info.afilias-nst.org, c0.info.afilias-nst.info, d0.info.afilias-nst.org
10
ns4-04.azure-dns.info: 13.107.160.4, 2620:1ec:bda::4
NS
a0.info.afilias-nst.info (2001:500:19::1)

Answer: ns4-01.azure-dns.info
13.107.160.1, 2620:1ec:bda::1

Answer: ns4-02.azure-dns.info
13.107.160.2, 2620:1ec:bda::2

Answer: ns4-03.azure-dns.info
13.107.160.3, 2620:1ec:bda::3
11
ru
NS
h.root-servers.net (2001:500:1::53)

Answer: a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net, f.dns.ripn.net
12
ns3.yandex.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.yandex.ru, ns2.yandex.ru, ns9.z5h64q92x9.net

Answer: ns1.yandex.ru
213.180.193.1, 2a02:6b8::1

Answer: ns2.yandex.ru
2a02:6b8:0:1::1, 93.158.134.1
13
ns4.yandex.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.yandex.ru, ns2.yandex.ru, ns9.z5h64q92x9.net

Answer: ns1.yandex.ru
213.180.193.1, 2a02:6b8::1

Answer: ns2.yandex.ru
2a02:6b8:0:1::1, 93.158.134.1
14
ns9.z5h64q92x9.net: 154.47.36.189, 2001:2030:20::78, 2001:978:7401::78, 80.239.201.9
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.yandex.net
213.180.193.1, 2a02:6b8::1

Answer: ns2.yandex.net
2a02:6b8:0:1::1, 93.158.134.1
15
ns3.yandex.ru: 87.250.250.1
A
ns1.yandex.ru (2a02:6b8::1)
16
ns3.yandex.ru: 2a02:6b8::1001
AAAA
ns1.yandex.ru (2a02:6b8::1)
17
ns4.yandex.ru: 77.88.21.1
A
ns1.yandex.ru (2a02:6b8::1)
18
ns4.yandex.ru: 2a02:6b8:0:1::1:1
AAAA
ns1.yandex.ru (2a02:6b8::1)
19
ns1.yandexcloud.net: 84.201.185.208
A
ns3.yandex.ru (2a02:6b8::1001)
20
ns1.yandexcloud.net: 2a0d:d6c1:0:1a::1b4
AAAA
ns3.yandex.ru (2a02:6b8::1001)
21
ns2.yandexcloud.net: 84.201.189.229
A
ns3.yandex.ru (2a02:6b8::1001)
22
ns2.yandexcloud.net: 2a0d:d6c1:0:1a::2c9
AAAA
ns3.yandex.ru (2a02:6b8::1001)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
bounce.mindbox.ru
0

no CAA entry found
1
0
mindbox.ru
5
issue
globalsign.com
1
0

5
issue
godaddy.com
1
0

5
issue
letsencrypt.org
1
0
ru
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
mindbox.ru
google-site-verification=KHBo2pnoozW8x93LYNlvdIk4seDmN-_QUy4zfPmojng
ok
1
0
mindbox.ru
google-site-verification=LwHj11hOwpYeFJGyaHTuYGCFEkPcG3IK051P54tkves
ok
1
0
mindbox.ru
loaderio=e107fe1ba2fef4ffc2728abdc7771a5c
ok
1
0
mindbox.ru
mindbox-alerts.azurewebsites.net
ok
1
0
mindbox.ru
MS=ms42412138
ok
1
0
mindbox.ru
MS=ms98765501
ok
1
0
mindbox.ru
oMPmrdd1MK2xEXhEPt++ZKqw77VFmn2cqUKvrNaFQHwSg6Y9sNF8dkXHe3SD4nYg3GC5Bw8pQchxgbUKdroWtA==
ok
1
0
mindbox.ru
status-page-domain-verification=4xzxt5q9lxjs
ok
1
0
bounce.mindbox.ru

ok
1
0
_acme-challenge.bounce.mindbox.ru

Name Error - The domain name does not exist
1
0
_acme-challenge.bounce.mindbox.ru.mindbox.ru

Name Error - The domain name does not exist
1
0
_acme-challenge.bounce.mindbox.ru.bounce.mindbox.ru

Name Error - The domain name does not exist
1
0


15. Portchecks

Domain or IPPortDescriptionResultAnswer
bounce.mindbox.ru
21
FTP



bounce.mindbox.ru
21
FTP



bounce.mindbox.ru
22
SSH



bounce.mindbox.ru
22
SSH



bounce.mindbox.ru
25
SMTP
open
220 bounce.mindbox.ru ESMTP

bounce.mindbox.ru
25
SMTP
open
220 bounce.mindbox.ru ESMTP

bounce.mindbox.ru
53
DNS



bounce.mindbox.ru
53
DNS



bounce.mindbox.ru
110
POP3



bounce.mindbox.ru
110
POP3



bounce.mindbox.ru
143
IMAP



bounce.mindbox.ru
143
IMAP



bounce.mindbox.ru
465
SMTP (encrypted)



bounce.mindbox.ru
465
SMTP (encrypted)



bounce.mindbox.ru
587
SMTP (encrypted, submission)



bounce.mindbox.ru
587
SMTP (encrypted, submission)



bounce.mindbox.ru
993
IMAP (encrypted)



bounce.mindbox.ru
993
IMAP (encrypted)



bounce.mindbox.ru
995
POP3 (encrypted)



bounce.mindbox.ru
995
POP3 (encrypted)



bounce.mindbox.ru
1433
MS SQL



bounce.mindbox.ru
1433
MS SQL



bounce.mindbox.ru
2082
cPanel (http)



bounce.mindbox.ru
2082
cPanel (http)



bounce.mindbox.ru
2083
cPanel (https)



bounce.mindbox.ru
2083
cPanel (https)



bounce.mindbox.ru
2086
WHM (http)



bounce.mindbox.ru
2086
WHM (http)



bounce.mindbox.ru
2087
WHM (https)



bounce.mindbox.ru
2087
WHM (https)



bounce.mindbox.ru
2089
cPanel Licensing



bounce.mindbox.ru
2089
cPanel Licensing



bounce.mindbox.ru
2095
cPanel Webmail (http)



bounce.mindbox.ru
2095
cPanel Webmail (http)



bounce.mindbox.ru
2096
cPanel Webmail (https)



bounce.mindbox.ru
2096
cPanel Webmail (https)



bounce.mindbox.ru
2222
DirectAdmin (http)



bounce.mindbox.ru
2222
DirectAdmin (http)



bounce.mindbox.ru
2222
DirectAdmin (https)



bounce.mindbox.ru
2222
DirectAdmin (https)



bounce.mindbox.ru
3306
mySql



bounce.mindbox.ru
3306
mySql



bounce.mindbox.ru
5224
Plesk Licensing



bounce.mindbox.ru
5224
Plesk Licensing



bounce.mindbox.ru
5432
PostgreSQL



bounce.mindbox.ru
5432
PostgreSQL



bounce.mindbox.ru
8080
Ookla Speedtest (http)



bounce.mindbox.ru
8080
Ookla Speedtest (http)



bounce.mindbox.ru
8080
Ookla Speedtest (https)



bounce.mindbox.ru
8080
Ookla Speedtest (https)



bounce.mindbox.ru
8083
VestaCP http



bounce.mindbox.ru
8083
VestaCP http



bounce.mindbox.ru
8083
VestaCP https



bounce.mindbox.ru
8083
VestaCP https



bounce.mindbox.ru
8443
Plesk Administration (https)



bounce.mindbox.ru
8443
Plesk Administration (https)



bounce.mindbox.ru
8447
Plesk Installer + Updates



bounce.mindbox.ru
8447
Plesk Installer + Updates



bounce.mindbox.ru
8880
Plesk Administration (http)



bounce.mindbox.ru
8880
Plesk Administration (http)



bounce.mindbox.ru
10000
Webmin (http)



bounce.mindbox.ru
10000
Webmin (http)



bounce.mindbox.ru
10000
Webmin (https)



bounce.mindbox.ru
10000
Webmin (https)



130.193.36.220
21
FTP



130.193.36.220
21
FTP



130.193.36.220
22
SSH



130.193.36.220
22
SSH



130.193.36.220
25
SMTP
open
220 bounce.mindbox.ru ESMTP

130.193.36.220
25
SMTP
open
220 bounce.mindbox.ru ESMTP

130.193.36.220
53
DNS



130.193.36.220
53
DNS



130.193.36.220
110
POP3



130.193.36.220
110
POP3



130.193.36.220
143
IMAP



130.193.36.220
143
IMAP



130.193.36.220
465
SMTP (encrypted)



130.193.36.220
465
SMTP (encrypted)



130.193.36.220
587
SMTP (encrypted, submission)



130.193.36.220
587
SMTP (encrypted, submission)



130.193.36.220
993
IMAP (encrypted)



130.193.36.220
993
IMAP (encrypted)



130.193.36.220
995
POP3 (encrypted)



130.193.36.220
995
POP3 (encrypted)



130.193.36.220
1433
MS SQL



130.193.36.220
1433
MS SQL



130.193.36.220
2082
cPanel (http)



130.193.36.220
2082
cPanel (http)



130.193.36.220
2083
cPanel (https)



130.193.36.220
2083
cPanel (https)



130.193.36.220
2086
WHM (http)



130.193.36.220
2086
WHM (http)



130.193.36.220
2087
WHM (https)



130.193.36.220
2087
WHM (https)



130.193.36.220
2089
cPanel Licensing



130.193.36.220
2089
cPanel Licensing



130.193.36.220
2095
cPanel Webmail (http)



130.193.36.220
2095
cPanel Webmail (http)



130.193.36.220
2096
cPanel Webmail (https)



130.193.36.220
2096
cPanel Webmail (https)



130.193.36.220
2222
DirectAdmin (http)



130.193.36.220
2222
DirectAdmin (http)



130.193.36.220
2222
DirectAdmin (https)



130.193.36.220
2222
DirectAdmin (https)



130.193.36.220
3306
mySql



130.193.36.220
3306
mySql



130.193.36.220
5224
Plesk Licensing



130.193.36.220
5224
Plesk Licensing



130.193.36.220
5432
PostgreSQL



130.193.36.220
5432
PostgreSQL



130.193.36.220
8080
Ookla Speedtest (http)



130.193.36.220
8080
Ookla Speedtest (http)



130.193.36.220
8080
Ookla Speedtest (https)



130.193.36.220
8080
Ookla Speedtest (https)



130.193.36.220
8083
VestaCP http



130.193.36.220
8083
VestaCP http



130.193.36.220
8083
VestaCP https



130.193.36.220
8083
VestaCP https



130.193.36.220
8443
Plesk Administration (https)



130.193.36.220
8443
Plesk Administration (https)



130.193.36.220
8447
Plesk Installer + Updates



130.193.36.220
8447
Plesk Installer + Updates



130.193.36.220
8880
Plesk Administration (http)



130.193.36.220
8880
Plesk Administration (http)



130.193.36.220
10000
Webmin (http)



130.193.36.220
10000
Webmin (http)



130.193.36.220
10000
Webmin (https)



130.193.36.220
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=c2d03385-481f-43ec-a465-31f6a3c6fb1c


Last Result: https://check-your-website.server-daten.de/?q=bounce.mindbox.ru - 2022-06-23 11:35:56


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=bounce.mindbox.ru" target="_blank">Check this Site: bounce.mindbox.ru</a>