Method of recording information on internet sites (embodiments)
Patent Information
- Application Number
- RU2025137128
- Authority / Receiving Office
- RU · RU
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2025-12-19
- Publication Date
- 2026-10-01
- Estimated Expiration
- 2045-12-19
Smart Images

Figure 00000001 
Figure 00000002 
Figure 00000003
Abstract
Description
[0001] The invention relates to the field of information technology, namely to systems and methods for documenting and recording the content of Internet resources, including information from a web page and screen images, for subsequent use as legally significant evidence [G06Q50 / 00, G06Q50 / 10, G06Q50 / 18].
[0002] The prior art discloses a SYSTEM AND METHOD FOR MONITORING FRAUDULENT USE OF ID AND A MEDIA FOR STORING THE SOURCE CODE OF A PROGRAM [KR20000063739A, publ. [06.11.2000], comprising a system for detecting identity theft during online access to servers via communication networks such as the Internet, wherein during initial membership registration, information about the hardware system of the user's terminal, including the BIOS serial number, CPU ID and other characteristics, is automatically extracted and stored together with the login data, including the first password, and the second password in a database, when connected online, the system authenticates the user using the first password and the captured hardware information by comparing it with the stored data, and in case of failure, uses the second password for additional verification, preventing unauthorized access and detecting theft, the system includes modules for membership management,Authentication and information provisioning systems running on a main server connected to a network with the ability to re-register when hardware changes, the method includes the steps of registration with hardware information retrieval, authentication with comparison and failure handling, and a recording medium such as a floppy disk or CD-ROM containing a program for implementing this process.
[0003] The disadvantage of this system and method for monitoring the fraudulent use of ID and storage media for storing program source code is that the system relies on extracting hardware information only during registration and authentication, without continuous monitoring or recording the state of the web page in real time, and data comparison requires additional steps with a second password, which may be prone to input errors or falsification, while the dependence on network connections and a database leads to potential delays and vulnerabilities in storage, and the lack of integration with visual or contextual captures of web pages makes verification subjective, and as a result, reduces the reliability of the recording of information on the web page.
[0004] Also known from the prior art is a METHOD AND SYSTEM FOR COLLECTING ELECTRONIC EVIDENCE FROM A WEB PAGE [CN103618649A, published 05.03.
[2014] , in which the user sends the URL of a web page and its content in the form of source code or a screenshot to the server via client software, the server generates a hash sum of the received data, receives a trusted timestamp from an authoritative time source, stores all materials together with the hash and timestamp in a database and issues an electronic confirmation certificate to the user, the system includes a client module for capturing the page content, a server module for processing, calculating the hash and receiving the timestamp, as well as a database for storing evidence with the possibility of subsequent verification, and the method provides for the stages of user authentication, data transfer, generation of an evidentiary package and notification of successful fixation, in addition, a digital signature of the server and encryption of the transmitted data can be used to protect against forgery.
[0005] The disadvantage of this method and system for collecting electronic evidence from a web page is that the recording depends on client software, which may be subject to manipulation or capture errors, and there is no automatic real-time verification of the page integrity without user intervention. In addition, storage is carried out on a centralized server without distributed verification, there are no mechanisms for recording dynamic content or multimedia, and the process requires active user actions and the transfer of large amounts of data, and as a result, reduces the reliability of recording information on the web page.
[0006] The closest in technical essence is the METHOD OF CAPTURE AND STORAGE OF INTERNET PAGE DATA [BR102019017526A2, published 02.03.2021], implemented in a system with a security server connected to the Internet and to the user's computer, where the server receives navigation commands from the user, in response to them, accesses content through an application stored and executed on the server, continuously transmits the graphical output generated by the application to the user's computer for monitoring, stores files, metadata and the full video file of the streaming, and at the end of the session generates a report with information about the session, file hash codes, a digital signature and a timestamp for integrity verification, the user's computer sends limited navigation commands, receives streaming for playback and can receive a report, while the method ensures the capture of dynamic content, with the removal of residual data after the session for security, as well as the addition of graphic markers in the video to indicate commands and screen captures.
[0007] The main technical problem with the prototype is that the method relies on streaming with potential delays, which can distort the real time of recording dynamic content; limiting navigation commands reduces the completeness of interaction with the web page, skipping some elements; and storage and capture occur on a centralized server without distributed verification, subject to the risk of compromise; the lack of automatic verification for manipulation during command transmission makes the process vulnerable to external influences, and as a result, reduces the reliability of recording information on the web page.
[0008] The objective of the invention is to eliminate the shortcomings of the prototype.
[0009] The technical result of the invention consists in increasing the reliability of recording information on a web page.
[0010] The reliability of information recording is understood as a complex property of recorded data that ensures its correspondence to the original state of the recording object at a specific point in time, as well as the possibility of subsequent independent verification of this correspondence, which is achieved through the use of cryptographic integrity control methods (hash sums), legally significant timestamps, immutable logging of metadata and the use of secure archives that exclude the possibility of unauthorized modification of both the primary content and accompanying service information.
[0011] The technical result is achieved due to the fact that the method of recording information on Internet sites is characterized by the fact that it includes the execution of successive stages, and
[0012] At the first stage, select a website page,
[0013] In the second stage, the information of the selected website page is recorded, while the URL of the page of the selected website and the URL of the image from the selected website page are copied,
[0014] In the third step, the URL of the page of the selected website and the URL of the image from the selected page of the website are inserted into the fixing site, at this step, the fixing site finds the position of the URL of the image from the selected page of the website, centers the selected page of the website and takes a screenshot of the selected page of the website,
[0015] At the fourth stage, a protocol is generated on the recording site, and a unique protocol identification number is generated for the protocol,
[0016] At the fifth stage, the protocol is saved on a dedicated server and a web copy of the selected website page.
[0017] In particular, an authorization stage is first carried out on the fixing site, where authorization is carried out using a username and password and a session token is generated using secure data transfer protocols.
[0018] In particular, at the second stage, the IP address of the website, WHOIS information about the domain, and the geolocation of the server of the selected website page are additionally collected.
[0019] In particular, at the fourth stage, the identification number is performed in the YYYYMMDDXXX format, where YYYY is the ordinal number of the year, MM is the ordinal number of the month, DD is the ordinal number of the day, XX is the ordinal number of the protocol, and at the same time, metadata is recorded, such as the IP address of the user's device, the version of the operating system, the version of the browser, the screen resolution, the hash sums of the URL of the image from the selected page of the website are calculated and the route is traced to the server of the selected page of the website and timestamps in UTC format are used for synchronization with the exact time servers using the NTP protocol.
[0020] In particular, at the fourth stage, the protocol includes a section called “Technical parameters and reliability assurance”, which includes details about the software used, server hardware, recording modes and measures for data immutability, such as timestamps and tracing checks. The protocol also includes a section called “Description of the recording process”, which details the automated actions: following a URL, capturing content, obtaining a unique session number, encrypting data and synchronizing time with NTP servers for accuracy in UTC format. Appendix No. 1 is generated in the protocol - screenshots of the page indicating the address, date and time, Appendix No. 2 - a printout of traces with route details and Appendix No. 3 - a copy of the computer program registration certificate, and a QR code or a unique identifier for accessing this protocol on a dedicated server is generated for each protocol.
[0021] In particular, at the fifth stage, a unique link is generated to access the protocol, which is saved in PDF format and a web copy of the selected website page.
[0022] Also, the technical result is achieved due to the fact that the method of recording information on Internet sites is characterized by the fact that it includes the implementation of sequential stages, and
[0023] At the first stage, select a website page,
[0024] In the second stage, the information of the selected website page is recorded, while the URL of the selected website page and the text information from the selected website page are copied,
[0025] In the third step, the URL of the selected website page and the copied text information from the selected website page are inserted into the fixing site. At this step, the fixing site finds the position of the copied text information on the page, centers the selected website page, and then takes a screenshot of the selected website page.
[0026] At the fourth stage, a protocol is generated on the recording site, and a unique protocol identification number is generated for the protocol,
[0027] At the fifth stage, the protocol is saved on a dedicated server and a web copy of the selected website page.
[0028] In particular, an authorization stage is first carried out on the fixing site, where authorization is carried out using a username and password and a session token is generated using secure data transfer protocols.
[0029] In particular, at the second stage, the IP address of the website, WHOIS information about the domain and the geolocation of the server of the selected page of the website are additionally collected.
[0030] In particular, at the fourth stage, the identification number is performed in the YYYYMMDDXXX format, where YYYY is the ordinal number of the year, MM is the ordinal number of the month, DD is the ordinal number of the day, XX is the ordinal number of the protocol, and at the same time, metadata is recorded, such as the IP address of the user's device, the version of the operating system, the version of the browser, the screen resolution, and the route is traced to the server of the selected website page and timestamps in UTC format for synchronization with the exact time servers using the NTP protocol.
[0031] In particular, at the fourth stage, the protocol includes a section called “Technical parameters and reliability assurance”, which includes details about the software used, server hardware, recording modes and measures to ensure data immutability, such as timestamps and tracing checks. The protocol also includes a section called “Description of the recording process”, which details the automated actions: following a URL, capturing content, obtaining a unique session number, encrypting data and synchronizing time with NTP servers for accuracy in UTC format. Appendix #1 is generated in the protocol - screenshots of the page indicating the address, date and time, Appendix #2 - a printout of traces with route details and Appendix #3 - a copy of the computer program registration certificate, and a QR code or a unique identifier for accessing this protocol on a dedicated server is generated for each protocol.
[0032] In particular, at the fifth stage, a unique link is generated to access the protocol, which is saved in PDF format and a web copy of the selected website page.
[0033] Also, the technical result is achieved due to the fact that the method of recording information on Internet sites is characterized by the fact that it includes the implementation of sequential stages, and
[0034] At the first stage, select a website page,
[0035] In the second stage, the information of the selected website page is recorded, while the URL of the selected website page is copied and a screenshot of the selected website page is generated,
[0036] At the third stage, the URL of the selected website page and the generated screenshot from the selected website page are inserted on the fixing site,
[0037] At the fourth stage, a protocol is generated on the recording site, and a unique protocol identification number is generated for the protocol,
[0038] At the fifth stage, the protocol is saved on a dedicated server and a web copy of the selected website page.
[0039] In particular, at the third stage, the site-fixer additionally breaks the selected website page into screenshots and saves these screenshots into the protocol at the next stage.
[0040] In particular, an authorization stage is first carried out on the fixing site, where authorization is carried out using a username and password and a session token is generated using secure data transfer protocols.
[0041] In particular, at the second stage, the IP address of the website, WHOIS information about the domain and the geolocation of the server of the selected page of the website are additionally collected.
[0042] In particular, at the fourth stage, the identification number is performed in the YYYYMMDDXXX format, where YYYY is the ordinal number of the year, MM is the ordinal number of the month, DD is the ordinal number of the day, XX is the ordinal number of the protocol, and at the same time, metadata is recorded, such as the IP address of the user's device, the version of the operating system, the version of the browser, the screen resolution, and the route is traced to the server of the selected website page and timestamps in UTC format for synchronization with the exact time servers using the NTP protocol.
[0043] In particular, at the fourth stage, the protocol includes a section called “Technical parameters and reliability assurance”, which includes details about the software used, server hardware, recording modes and measures to ensure data immutability, such as timestamps and tracing checks. The protocol also includes a section called “Description of the recording process”, which details the automated actions: following a URL, capturing content, obtaining a unique session number, encrypting data and synchronizing time with NTP servers for accuracy in UTC format. Appendix No. 1 is generated in the protocol - screenshots of the page indicating the address, date and time, Appendix No. 2 - a printout of traces with route details and Appendix No. 3 - a copy of the computer program registration certificate, and a QR code or a unique identifier for accessing this protocol on a dedicated server is generated for each protocol.
[0044] In particular, at the fifth stage, a unique link is generated to access the protocol, which is saved in PDF format and a web copy of the selected website page.
[0045] Brief description of drawings.
[0046] Fig. 1 shows the main page of the fixer site.
[0047] Fig. 2 shows the interface of the fixer site.
[0048] Fig. 3 shows the selected page of the website with the URL indicated.
[0049] Fig. 4 shows the interface of the site-recorder for recording information by the URL of an image from a selected page of the website.
[0050] Fig. 5 shows the generated protocol for the image URL from the selected page of the website.
[0051] Fig. 6 shows Appendix No. 1 of the protocol for the URL of an image from a selected page of an Internet site.
[0052] Fig. 7 shows Appendix No. 2 of the protocol for the URL of an image from a selected page of an Internet site.
[0053] Fig. 8 shows Appendix No. 3 of the protocol.
[0054] Fig. 9 shows the interface of the site-recorder for recording information on text information from the selected page of the website.
[0055] Fig. 10 shows the generated protocol based on text information from the selected page of the website.
[0056] Fig. 11 shows Appendix No. 1 of the protocol on text information from the selected page of the website.
[0057] Fig. 12 shows Appendix No. 2 of the protocol on text information from the selected page of the website.
[0058] Fig. 13 shows the interface of the site that records the execution of information recording based on a screenshot from a selected page of the website.
[0059] Fig. 14 shows the generated protocol based on a screenshot from the selected website page.
[0060] Fig. 15 shows Appendix No. 1 of the protocol based on a screenshot from the selected page of the website.
[0061] Fig. 16 shows Appendix No. 2 of the protocol based on a screenshot from the selected page of the website.
[0062] Implementation of the invention.
[0063] The method for recording information on websites includes performing successive steps, wherein at the first step, a website page is selected, at the second step, information from the selected website page is recorded, while the URL of the page of the selected website and the URL of the image from the selected website page are copied, at the third step, the URL of the page of the selected website and the URL of the image from the selected website page are inserted on the recording site, at this step, the recording site finds the position of the URL of the image from the selected website page, centers the selected website page and takes a screenshot of the selected website page, at the fourth step, a protocol is formed, while a unique protocol identification number is generated for the protocol, at the fifth step, the protocol is saved on a dedicated server and a web copy of the selected website page is created.
[0064] Also, the method of recording information on Internet sites includes performing sequential steps, wherein at the first step, a page of the Internet site is selected, at the second step, information from the selected page of the Internet site is recorded, while the URL of the selected page of the Internet site and text information from the selected page of the Internet site are copied, at the third step, the URL of the selected page of the Internet site and the copied text information from the selected page of the Internet site are inserted on the recording site, at this step, the recording site finds the position of the copied text information on the page, centers the selected page of the Internet site, then takes a screenshot of the selected page of the Internet site, at the fourth step, a protocol is formed, while a unique protocol identification number is generated for the protocol, at the fifth step, the protocol is saved on a dedicated server and a web copy of the selected page of the Internet site is created.
[0065] Also, a method for recording information on Internet sites is characterized by the fact that it includes the execution of sequential stages, wherein at the first stage a page of the Internet site is selected, at the second stage the information of the selected page of the Internet site is recorded, while the URL of the selected page of the Internet site is copied and a screenshot of the selected page of the Internet site is formed, at the third stage the URL of the selected page of the Internet site and the formed screenshot from the selected page of the Internet site are inserted on the recording site, at the fourth stage a protocol is formed, while a unique identification number of the protocol is generated for the protocol, at the fifth stage the protocol is saved on a dedicated server and a web copy of the selected page of the Internet site is created.
[0066] The URL of a selected website page is understood to be a unique address identifier - a Uniform Resource Locator, which uniquely identifies the location of a specific web page on the Internet and allows it to be accessed through a browser; this address includes such elements as the protocol used (e.g., HTTP or HTTPS), the site's domain name, the path to the page and, if available, query parameters, which together provide an exact link to the recorded content for its subsequent identification and verification in the process of generating evidence.
[0067] The URL of an image from a selected website page is understood to be the full absolute address (Uniform Resource Locator) that points to a specific graphic file (e.g., in JPEG, PNG, or GIF format) hosted on a web server and displayed on the captured page; this address allows for the unambiguous identification and subsequent access to this media object for its storage, authentication, and inclusion in the capture protocol as evidence.
[0068] A screenshot is a static digital image (snapshot) obtained by capturing the contents of a monitor screen or an area of a web page at a specific moment in time, which accurately visually reproduces the information displayed, including text, graphics, interface elements and their location, and which is supplied with metadata (e.g., timestamp, hash sum) to confirm its authenticity, immutability and correspondence to the original content at the time of capture.
[0069] The unique identification number of the protocol is understood to be an automatically generated digital code in a structured format (YYYYMMDDXXX), which is assigned to each created recording protocol, serves for its unambiguous identification and indexing in the database of a dedicated server, provides protection against duplication and falsification, and is also used for subsequent searching, verification and provision of access to the document and its web copy via a QR code or direct link.
[0070] Centering refers to the automated process of positioning the view of a web page in a browser or emulator so that a located element (the position of an image URL or copied text information) is in the center of the virtual screen before taking a screenshot, this includes scrolling the page to the coordinates of the element, calculating its frame using DOM analysis, and adjusting its area to ensure that the element is placed symmetrically relative to the edges of the frame, which ensures its clear visibility and focus in the screenshot, minimizing distortion and increasing the evidentiary value of the captured image in the protocol.
[0071] A dedicated server is a dedicated and isolated server infrastructure that functions as an independent web archive, providing long-term, secure, and immutable storage of generated commit logs and their web copies in encrypted form, using backups on distributed nodes, strict access protocols (such as HTTPS), and digital signatures to guarantee the integrity, authenticity, and legal validity of stored materials, excluding the possibility of their unauthorized modification or deletion.
[0072] A web copy is a complete and unmodified archive copy of a selected web page, created at the time of fixation, which includes all source code (HTML, CSS, JavaScript), media resources (images, fonts) and metadata, allows for the exact reproduction of the appearance, functionality and content of the page in its original state, is stored on a dedicated server in conjunction with a protocol under a unique identifier and is supplied with check hash sums to ensure legal significance, verifiable integrity and long-term availability as irrefutable evidence.
[0073] Metadata refers to systematized service information that describes the context, characteristics, and circumstances of the recording process, including technical parameters (IP address, browser version, screen resolution, hash sums), UTC timestamps, trace data, session identifiers, and user device information, and which is used to confirm the authenticity, immutability, and reliability of the collected evidence, ensuring its legal significance and the possibility of independent verification.
[0074] The method of recording information on Internet sites is performed as follows.
[0075] The recording site first undergoes an authorization process. Authorization is performed using a username and password, and a session token is generated using secure data transfer protocols (Fig. 1). A user wishing to initiate the recording process on the website first navigates to the recording site's main page, where they are presented with a login interface. This interface consists of an authorization form containing fields for entering a username (login) and password. The username can be a unique identifier, such as an email address or a nickname, which is registered in advance when creating an account. The password, in turn, is a confidential string of characters that provides protection from unauthorized access.It's important to note that the recording site uses secure data transfer protocols, such as HTTPS, to prevent information interception during transmission, enhancing the overall security and reliability of subsequent recording stages. After entering the data, the user clicks the "Login" button, which initiates the verification process on the server.
[0076] Secure data transfer protocols are network communication protocols that use cryptographic methods (such as encryption, authentication, and transmission integrity) to securely exchange information between a client and a server, preventing interception, substitution, or distortion of data throughout the communication channel; the most common example is the HTTPS (HyperText Transfer Protocol Secure) protocol, which runs on top of the TLS (Transport Layer Security) encryption protocol or its predecessor, SSL (Secure Sockets Layer), which ensures the confidentiality of transmitted information, authentication of the parties, and protection against man-in-the-middle attacks, which is critical to ensuring the legal validity and reliability of the recording process, excluding the possibility of unauthorized access or modification of data during its transmission from the user to the recording site and then to the dedicated storage server.
[0077] The authentication of the entered data occurs on the recording site's server: the system compares the provided username against the database of registered accounts and, if a match, verifies the password hash using cryptographic algorithms to avoid storing passwords in cleartext. If the username is not found or the password does not match, the system returns an error message, "Incorrect username or password," prompting the user to re-enter. If authorization is successful, the server generates a session token, which is associated with the user's account and allows the user to maintain an authenticated state throughout the entire session. Furthermore, to enhance the legal validity of the recording, the system can record authorization metadata, including the user's IP address, login time, and device used for access, which can subsequently be used in the protocol as proof of the authenticity of the initiator of the process.This approach ensures traceability and prevents counterfeiting at the initial stage.
[0078] After successful authorization, the user is redirected to the recording site interface, where they can perform further steps, such as specifying the URL of the selected website page and pasting information in the form of an image URL from the selected website page, text information from the selected website page, or attaching a screenshot from the selected website page (Fig. 2). This step not only ensures security but also lays the foundation for the legal validity of the entire information recording process, as the authorized user is responsible for the initiated actions, and the system guarantees that all subsequent steps are associated with the verified identity. This avoids disputes over the authenticity of the recorded materials in court or administrative courts.
[0079] In the first step, select a website page. This step begins with searching or directly specifying the URL of the selected website page where the violation is suspected, such as illegal use of content, copyright infringement, dissemination of disinformation or other illegal activities.
[0080] In the second stage, the information of the selected website page is recorded, while the URL of the selected website page is copied, as well as the URL of the image from the selected website page, or the text information is copied from the selected website page, or a screenshot of the selected website page is generated.
[0081] Thus, while capturing information from a selected website page, the user can copy the URL of an image or other media element if the violation is related to visual content. If the violation is in text format, the user selects and copies the text fragment directly from the selected website page. The system preserves not only the text itself but also its context, such as surrounding paragraphs, formatting (bold, italics), and position on the page. For cases where the violation involves more than simple copying, the user creates a screenshot of a specific section of the selected website page.
[0082] The second stage additionally collects the website's IP address, domain WHOIS information, and the server geolocation of the selected website page. These are automatically retrieved using the APIs of external services integrated into the recording site to ensure complete identification and prevent substitution or masking of the selected website page. This allows not only for the precise localization of the source of the violation but also for recording time characteristics, such as the date and time of detection, which is critical for the legal validity of subsequent actions.
[0083] WHOIS information about a domain is publicly available registration data about a domain name obtained by querying the relevant database (WHOIS server), which includes information about the domain owner (registrant), administrator, technical contact, registration and expiration dates, as well as information about the registrar and DNS servers, and which is used to identify the entity responsible for the content of the website, establish its legitimacy and prevent anonymity when violations are recorded.
[0084] Once the information has been captured, the collected data - URLs of elements, text fragments, or screenshots - is temporarily stored in the local storage of the capturing site associated with the authorized user account, with automatic encryption to protect against unauthorized access.
[0085] In the third step, the URL of the selected website page is pasted onto the fixer site, along with the URL of an image from the selected website page, copied text information from the selected website page, or a generated screenshot from the selected website page. The user can manually enter the URL of the selected website page in a special field, ensuring accurate entry to avoid errors, or use the paste function by copying the URL of the selected website page and pasting it into the Site URL field on the fixer site.
[0086] Also at this stage, the site fixer finds the position of the image URL from the selected website page or the position of the copied text information on the page, centers the selected website page, and then takes a screenshot of the selected website page.
[0087] This stage is completed by clicking the "Create Protocol" button, after which the data is marked as ready for transfer to the next stage, without further manipulation. This approach ensures minimalism and a focus on collecting primary evidence, minimizing the risk of information distortion, and lays the foundation for subsequent processing, where these materials will be integrated into legally significant documents. Overall, the recording stage emphasizes the "what you see is what you record" principle, with an emphasis on objectivity and technical accuracy, which increases the overall credibility of the entire process of documenting website violations.
[0088] In the fourth stage, a protocol is generated on the recording site. After the information recording stage is complete and the user clicks the "Create Protocol" button on the recording site, the system automatically initiates the process of compiling all collected data into a single legally binding document. At this stage, a unique protocol identification number is generated for the protocol, which is in the format YYYYMMDDXXX, where YYYY is the year, MM is the month, DD is the day, and XX is the protocol number. Also recorded at this stage are metadata, such as the user's device IP address, operating system version, browser version, and screen resolution. The hash sums of the image URL from the selected website page are calculated, the route to the server of the selected website page is traced, and UTC timestamps are added for synchronization with NTP time servers.To ensure authenticity, the system uses cryptographic methods: hash sums are calculated for each data element, including images and logs, and the route to the server of the selected website page is traced to confirm availability and the absence of tampering. All this is automated and occurs on a dedicated server, where data is transmitted over a secure HTTPS channel with encryption, eliminating the possibility of interference or modification by the user or third parties. This results in a protocol header indicating the start date and time of generation, as well as general information about the capture.
[0089] NTP synchronization (NTP protocol) refers to the process of automatically coordinating a device's system time with reference time servers using the NTP (Network Time Protocol), which ensures millisecond accuracy of timestamps through the use of a hierarchical system of stratums and network delay compensation algorithms. This is critical for the legal validity of recording, as it guarantees a single time space for all participants in the process and prevents possible time discrepancies that could call into question the reliability of event documentation.
[0090] Next, the system structures the protocol into predefined sections based on the computer program template to ensure compliance with legal requirements.The protocol includes a section called "Technical Parameters and Validity Ensuring" which includes details about the software used, server hardware, recording modes, and data immutability measures such as timestamps and trace checks. The protocol also includes a section called "Description of the Recording Process" which details the automated actions: following a URL, capturing content, obtaining a unique session number, encrypting data, and synchronizing time with NTP servers for accuracy in UTC format. Appendix #1 is generated in the protocol - screenshots of the page indicating the address, date, and time, Appendix #2 - a printout of traces with route details, and Appendix #3 - a copy of the computer program registration certificate. A QR code or a unique identifier for accessing the given protocol on a dedicated server is also generated for each protocol.
[0091] The "Description of the Capture Process" section of the protocol details automated actions: URL navigation, content capture, obtaining a unique session number, data encryption, and time synchronization with NTP servers for UTC accuracy. The results of scheduled technical inspections confirming the system's functionality and the absence of signs of tampering are also recorded here. To enhance legal validity, links to external resources, such as the FIPS registry, are integrated, and the protocol can be verified by any interested party via a QR code or unique identifier. All sections are generated in PDF format with watermarks and a server digital signature, guaranteeing integrity and reproducibility.
[0092] Additionally, a "Legal Justification and Compliance" section is created in the protocol. The recording site automatically inserts links to regulations and case law adapted to the context of the information being recorded, emphasizing the relevance, admissibility, and reliability of the evidence. This includes an argument that the protocol meets the requirements for screenshots as evidence, noting the stability of the results and the independence of the recording. Upon completion, the protocol undergoes final validation: checking for the presence of all elements, calculating checksums, and generating a digital certificate of authenticity. The completed document is displayed to the user for viewing and downloading. This stage concludes with logging of the event in the server system log, including metadata about the creation, which allows for future auditing and confirmation in court.Overall, the automated approach ensures objectivity by minimizing human error and increases the reliability of violation recording through the comprehensive integration of technical, legal, and security mechanisms, making the protocol fully valid evidence in accordance with Russian law.
[0093] In the fifth stage, the protocol is saved on a dedicated server and a web copy of the selected website page is created. Once the protocol is generated, the website's recording system automatically initiates the process of transferring the completed document to a dedicated server, which functions as a web archive, ensuring long-term and secure storage of all generated protocols. This server is an independent infrastructure managed by disinterested parties, where data is stored encrypted using HTTPS transfer protocols and additional encryption measures to prevent unauthorized access or modification. The protocol is saved in PDF format under a unique identification number, which is generated during the protocol generation stage and serves as the indexing key.During the storage process, the system calculates hash checksums for the entire file and its attachments and adds a server digital signature confirming its integrity and authenticity. Storage metadata, including the date and time of storage, the source IP address, and the software version, are recorded in the server system log to ensure traceability, enabling future auditing and verification, eliminating the possibility of data tampering, as specified in the evidence reliability requirements.
[0094] The dedicated server is organized as a distributed storage system, similar to a web archive, where each protocol is archived immutably with backups on multiple nodes to increase fault tolerance and availability. Storage is performed in a structured database, where the protocol is associated with the user's session number, but without revealing personal data, thus upholding privacy principles.
[0095] In addition to the protocol, a web copy of the selected website page is stored on a dedicated server. This web copy represents a complete archive of the web page in a format that allows the selected page to be played back in its entirety, as loaded at the time of capture. This web copy of the selected website page is automatically generated based on the data collected in the previous steps, using capture tools to emulate a real view and preserve dynamic content unchanged. The web copy of the selected website page is stored in the same secure server environment, assigned the same unique identifier as the protocol, and hash sums are calculated for each component to ensure immutability and independent verification.Access to a web copy of the selected website page is provided through a generated link that is displayed after the protocol is created, and this link allows interested parties, such as courts or experts, to reproduce the page in its original form at any time, which enhances the legal significance of the recording.
[0096] Upon completion of the recording, the recording site generates a unique link to access the protocol, which is displayed to the user in the interface. This link allows access to the archive at any time, enabling reproducible viewing or downloading of the protocol with attachments without the need for re-authorization, but with optional verification via a QR code or digital signature to confirm authenticity. The user can share the link with third parties, such as lawyers or courts, where the protocol will serve as legally binding evidence. This stage thus completes the information recording cycle, emphasizing the principle of permanent availability and immutability of materials, which increases the overall reliability of the system and its value for documenting online violations.
[0097] At the first stage, a website page is selected, thus this stage is the starting point and a fundamental condition for subsequent reliable recording, since it is this stage that unambiguously defines the object of documentation - a specific web resource with a unique URL, which eliminates uncertainty in the identification of the recorded content, prevents possible errors or disputes regarding the source of information, and thereby ensures the focus and accuracy of all subsequent evidence collection operations, and, as a result, increases the reliability of the recording of information on the web page.
[0098] The second stage involves recording information from the selected website page, thereby ensuring the collection of primary material evidence - URL addresses, text content, images or screenshots - which creates an immutable digital basis for subsequent logging, while simultaneously automatically collecting additional identifying data, such as IP address, WHOIS information and server geolocation, which allows for the unambiguous linking of recorded content to a specific source (website page) and point in time, eliminating the possibility of substitution or disputing the original, and, as a result, increases the reliability of recording information on the web page.
[0099] Copying the page URL of a selected website and the image URL from the selected page of the website ensures the creation of an interconnected and verifiable chain of evidence, where the page URL uniquely identifies the source of the content, and the image URL allows direct access to a specific media object, recording its digital address and providing the ability to independently verify the authenticity and immutability of the recorded visual material, and, as a result, increases the reliability of the recording of information on the web page.
[0100] Copying the URL of a selected website page and the text information from the selected page ensures the creation of an unbreakable link between the unique address identifier of the resource and its actual content, which makes it possible to unambiguously prove the origin of the text content from a specific source and eliminates the possibility of subsequent dispute or alienation of the recorded information from its original location, and, as a result, increases the reliability of the recording of information on the web page.
[0101] Copying the URL of a selected website page and creating a screenshot of the selected page provides a comprehensive record, where the URL uniquely identifies the digital address of the source, and the screenshot visually documents the actual state and content of the page at a specific point in time, thereby creating a coherent and clear evidence base that eliminates the possibility of challenging the authenticity of the recorded information and its affiliation with the specified web resource, and, as a result, increases the reliability of the recording of information on the web page.
[0102] Inserting the URL of the selected website and the URL of the image from the selected page on the recording site in the third stage ensures the integration of the collected evidence into a secure processing environment, where it is automatically verified, cryptographically linked, and included in the generated protocol, which creates an officially recorded and legally significant link between the content source and a specific media object, eliminating the possibility of unauthorized modification of data after its transmission to the system, and, as a result, increases the reliability of the recording of information on the web page.
[0103] Inserting the URL of the selected website page and the copied text information on the recording site at the third stage ensures the official integration of the primary data into a secure logging environment, where they are automatically verified, cryptographically linked, and timestamped, creating a legally significant and immutable link between the source identifier and the actual text content, eliminating the possibility of subsequent alienation or modification of the text after it is transmitted to the system, and, as a result, increases the reliability of the recording of information on the web page.
[0104] Inserting the URL of the selected website page and the generated screenshot on the recording site in the third stage ensures the creation of an unbroken chain of evidence in a secure environment, where the unique address of the page unambiguously identifies the source, and the visual snapshot, supplemented with metadata, objectively records its actual content and visual state at the time of access, which eliminates the possibility of subsequent disputes regarding both the content's affiliation with the specified resource and its original appearance, and, as a result, increases the reliability of the recording of information on the web page.
[0105] The site fixer finds the position of the image URL from the selected website page, centers the selected website page and takes a screenshot of the selected website page, which provides automated, accurate and complete visual documentation of the context in which the sought media object is located, eliminating subjective errors in manual selection of the capture area, ensuring that the screenshot will capture not only the image itself, but also the surrounding page elements, confirming its actual placement and the unchanged composition of the web document at the time of capture, and as a result, the reliability of the capture of information on the web page is increased.
[0106] The website fixer locates the copied text information on the page, centers the selected website page, and then takes a screenshot of the selected website page, which provides automatic and accurate visual documentation of not only the text fragment itself, but also its immediate context, location, formatting, and surrounding interface elements on the web page, eliminating subjective errors in manually selecting the capture area and ensuring that the screenshot objectively reflects the true representation of the text in the document structure, which confirms the immutability of its semantic and visual context at the time of recording, and as a result, the reliability of recording information on the web page is increased.
[0107] The fourth stage of protocol generation on the recording site ensures the systematization and legal registration of all recorded data into a single structured document that combines primary evidence (URL, text, images, screenshots) with verification metadata (timestamps, hash sums, traces), thereby creating a complete, cryptographically protected and immutable evidence base suitable for independent verification and judicial use, and, as a result, increases the reliability of the information recorded on the web page.
[0108] Generating a unique protocol identification number ensures the unambiguous individualization and traceability of each recording act, creating a structured and duplication-protected indexing system that allows for the precise identification, retrieval, and verification of the corresponding protocol and all related materials in the dedicated server database, eliminating the possibility of document substitution and ensuring the integrity of the evidence chain, and, as a result, increases the reliability of the information recorded on the web page.
[0109] Saving the protocol on a dedicated server and a web copy of the selected website page in the fifth stage ensures long-term, immutable and secure storage of all evidence in a centralized secure archive, where the protocol containing metadata and verification results and the web copy, which accurately reproduces the original state of the page, are cryptographically linked and stored in their integrity, which guarantees their availability for subsequent independent verification, eliminates the possibility of loss or modification of materials after recording and gives the collected evidence the property of irrefutability, and, as a result, increases the reliability of recording information on the web page.
[0110] The technical result is achieved due to the fact that the method for recording information on Internet sites includes the implementation of successive stages, wherein at the first stage a page of the Internet site is selected, at the second stage the information of the selected page of the Internet site is recorded, while copying the URL of the page of the selected Internet site and the URL of the image from the selected page of the Internet site, at the third stage the URL of the page of the selected Internet site and the URL of the image from the selected page of the Internet site are inserted on the recording site, at the fourth stage a protocol is formed on the recording site, while a unique protocol identification number is generated for the protocol, at the fifth stage the protocol is saved on a dedicated server and a web copy of the selected page of the Internet site is saved, thereby the entire set of features creates a synergistic effect, where each stage strengthens and complements the previous one,Forming a closed-loop system with multiple duplication and cross-checking of information. Selecting a page in the first stage ensures precise identification of the captured object, and copying the page URL and image in the second stage creates a dual link—to both the source as a whole and to specific media content. Inserting this data into the capturing site in the third stage ensures its verification in a controlled environment, and generating a protocol with a unique identifier in the fourth stage gives the collected data a legally binding form. Finally, storing the protocol and web copy on a dedicated server in the fifth stage guarantees the immutability and long-term availability of evidence. This multi-level system, where each protocol element is interconnected and protected from modification, eliminates the possibility of falsification at any stage and enables independent verification of the authenticity of the captured information.which ultimately leads to the achievement of the stated technical result - increasing the reliability of recording information on the web page.
[0111] Also, the technical result is achieved due to the fact that the method of recording information on Internet sites is characterized by the fact that it includes the execution of sequential stages, and at the first stage, a page of the Internet site is selected, at the second stage, the information of the selected page of the Internet site is recorded, while the URL of the selected page of the Internet site and the text information from the selected page of the Internet site are copied, at the third stage, the URL of the selected page of the Internet site and the copied text information from the selected page of the Internet site are inserted on the recording site, at the fourth stage, a protocol is formed on the recording site, while a unique protocol identification number is generated for the protocol, at the fifth stage, the protocol is saved on a dedicated server and a web copy of the selected page of the Internet site is saved, thereby the entire set of features forms an integral system of documentary confirmation of text content,Where the sequential implementation of stages ensures the continuity of the evidentiary chain. The initial selection of a page defines a specific object of capture, while copying the URL and text information in the second stage creates a paired link—the source identifier and its actual semantic content. Integration of this data on the capture site in the third stage enables their cryptographic binding and verification of authenticity, and the formation of a protocol with a unique identifier in the fourth stage gives the collected evidence a structured legal form. The final storage of the protocol and web copy on a dedicated server guarantees the long-term preservation and immutability of both the completed document and the original state of the page. Of particular importance is the combination of text information with the web copy, allowing for cross-checking of the content through direct comparison with the archived version of the page. This multifaceted approach,ensuring mutual verification of various forms of content and their reliable archiving, creates the most reliable recording system, eliminating the possibility of subsequent disputing the authenticity or context of the recorded text information.
[0112] Also, the technical result is achieved due to the fact that the method of recording information on Internet sites is characterized by the fact that it includes the execution of sequential stages, and at the first stage, a page of the Internet site is selected, at the second stage, information of the selected page of the Internet site is recorded, while the URL of the selected page of the Internet site is copied and a screenshot of the selected page of the Internet site is generated, at the third stage, the URL of the selected page of the Internet site and the generated screenshot from the selected page of the Internet site are inserted on the recording site, at the fourth stage, a protocol is generated on the recording site, while a unique protocol identification number is generated for the protocol, at the fifth stage, the protocol is saved on a dedicated server and a web copy of the selected page of the Internet site is created, thereby the entire set of features creates a comprehensive system of visual documentation of web content,Where step-by-step implementation ensures the formation of complementary evidence. Selecting a page in the first step determines the object of capture, and the combination of URL copying and screenshot creation in the second step establishes double confirmation—both the digital address of the source and its visual representation at a specific point in time. Integration of these elements on the capture site in the third step enables their cryptographic linking and technical verification, and the generation of a protocol with a unique identifier in the fourth step gives the collected materials legal status. Final storage of the protocol and web copy on a dedicated server ensures the long-term preservation and immutability of both the completed document and the archived version of the page. The combination of a screenshot, capturing the visual state of the interface and content, with a full web copy lends particular evidentiary force to this implementation option.Allowing for a detailed technical examination of the source code and additional resources. This multi-layered approach, which ensures cross-checking of the page's visual and technical characteristics, creates the most comprehensive system of verification, eliminating the possibility of subsequent disputes regarding the authenticity of the appearance, content, or functional elements of the verified web page.
[0113] An example of the implementation of a method for recording violations on Internet sites.
[0114] The first implementation example is a method for capturing information from a website using an image URL. To demonstrate the practical implementation of the proposed method for capturing information on websites, we will consider a specific example. Let's assume that a user wants to capture information from a news website page containing an article about current events in order to preserve evidence of its content at a specific point in time. This may be useful for legal purposes, archiving, or data verification. We use the Fixator service (https: / / fixator-app.ru / ) (hereinafter referred to as the fixator site) as the capture site (Fig. 1). All actions were performed in a web browser on the user's device (a PC with Windows 11 OS, Google Chrome version 120.0, screen resolution 1920x1080).
[0115] Before recording information, the user logged in to the recording site to ensure security and personalization of the process. The user opened the recording site's main page and entered their username. After successful authorization, the system generated a session token using secure data transfer protocols such as HTTPS and TLS 1.3, and the token was saved in the browser cookie for the duration of the session.
[0116] After authorization, the user is directed to the main interface of the fixation site (Fig. 2). Here, options for starting a new fixation, the history of previous protocols, and account settings are displayed.
[0117] At this stage, the user selected a website page to be captured. In this case, this is the page https: / / obrnadzor.gov.ru / news / izmenenie-trebovanij-k-sochineniyu-v-ege-po-russkomu-yazyku-povysilo-obektivnost-ekzamena / . This page contains the article text, images, and metadata (Fig. 3). The page was selected by opening it in a browser and checking the relevance of the information. The user ensured that the page loaded completely, without errors, and contained the required elements (text, images, links). This is a basic step that ensures that the capture will be made on relevant content.
[0118] Next, we proceeded to the second stage and recorded information from the selected page. The user copied the page URL (https: / / obrnadzor.gov.ru / news / izmenenie-trebovanij-k-sochineniyu-v-ege-po-russkomu-yazyku-povysilo-obektivnost-ekzamena / ) and the URL of the image on it (https: / / obrnadzor.gov.ru / wp-content / uploads / 2025 / 06 / 121.jpg). This is done manually: right-click the image and select "Copy image URL," and then copy the page URL from the browser's address bar.
[0119] At the third stage, the copied URLs were pasted into the corresponding fields in the recording site interface (Fig. 2): the "Page URL" field - https: / / obrnadzor.gov.ru / news / izmenenie-trebovanij-k-sochineniyu-v-ege-po-russkomu-yazyku-povysilo-obektivnost-ekzamena / , the "Image URL" field - https: / / obrnadzor.gov.ru / wp-content / uploads / 2025 / 06 / 121.jpg. In addition, at this stage, the recording site found the position of the image URL from the selected website page, centered it, and took a screenshot of the selected website page. After entering, the "Create protocol" button was clicked on the recording site, which launched the automated protocol creation process.
[0120] At this fourth stage, the capture site system automatically generated a log (Fig. 4). The computer (the capture site server, running Linux) initiated a sequence of automated actions: first, it generated a unique log identification number in the format YYYYMMDDXXX (20251126154, where 2025 is the year, 11 is the month, 26 is the day, and 154 is the daily log sequence number) using a built-in Python script (the datetime library for retrieving the current date and a MySQL-based incremental counter for the sequence number). This is ensured by an atomic operation in the database to avoid duplicates during concurrent requests from multiple users.
[0121] The computer then recorded the user's device metadata: the IP address obtained from the HTTP request via the X-Forwarded-For header, the OS version determined from the browser's User-Agent string, the browser version (also from the User-Agent string), and the screen resolution transmitted via a JavaScript script on the client and sent to the server. This data was serialized in JSON format and stored in a temporary Redis cache for quick access during protocol generation.
[0122] The computer calculated the hash sum of the image URL (SHA-256) using the hashlib library in Python; the hash is generated based on the binary content of the image downloaded from the URL via requests.get()), and also traced the route to the target site's server using the traceroute utility in Linux, which sends ICMP packets and records hops, for example: hop 1 - local router 192.168.1.1, hop 2 - ISP gateway, and so on to the final server obrnadzor.gov.ru with IP 195.208.1.100, the results are parsed and formatted into a text log. Timestamps are added in UTC format, synchronized with NTP servers, the computer contacts pool.ntp.org via NTP protocol every 10 minutes to adjust the system time, using the ntplib library to ensure millisecond accuracy and prevent clock drift.
[0123] Thus, the fixation process included the following automated computer actions:
[0124] - Navigating to the URL https: / / obrnadzor.gov.ru / news / izmenenie-trebovanij-k-sochineniyu-v-ege-po-russkomu-yazyku-povysilo-obektivnost-ekzamena / (the server sends an HTTP GET request through a headless browser based on Puppeteer or Selenium, simulating a user's browsing experience, with the time of capture being 16:40 UTC; this includes rendering the page, executing JavaScript, and capturing the DOM structure).
[0125] - Full content capture (2025-11-26 16:40: The server downloads HTML, CSS, JS and media files using wget or a similar tool in recursive mode, saving them to a local archive; the size of the captured data is about 500 KB, including the image 121.jpg).
[0126] Before the automatic recording service "Fixator" began recording information, the following was performed:
[0127] - Contacting the Linux inilaw-vm server to obtain a unique session number (the computer generates a UUID v4 using the uuid library corresponding to the protocol number and stores it in the database; the session is associated with the user token for authentication).
[0128] - Data received from the user's device has been encrypted (using AES-256 with a key generated from the user's password via PBKDF2; encryption is applied to metadata and content before transmission over HTTPS).
[0129] - When the Automatic Recording Service "Fixer" was launched, it contacted the exact time server via the NTP protocol to synchronize the application's system time in order to accurately determine the time of recording the information (the computer executes ntpdate or a similar command, adjusting the offset, for example, by 5 ms; for greater reliability, the time of image creation is given in the protocol in UTC format).
[0130] - After the recording of the information displayed on the user's device is completed, the received data and images are automatically transferred in encrypted form via a secure channel to the "Linux inilaw-vm" server (transfer via SFTP or HTTPS POST with chunked encoding for large files; on the server, the data is decrypted and a protocol is generated based on it using the Jinja2 template engine for generating HTML / PDF).
[0131] - During a scheduled technical inspection on October 31, 2025, technical support specialists checked the operability of hardware and software, compliance with technical conditions that prevent data substitution during the recording of information and during its storage (this includes automated tests: running scripts to check integrity (md5sum on files), monitoring logs using ELK Stack and verifying digital signatures with RSA-2048).
[0132] - Using route tracing software, the Service checked the availability of the end node (server) where the information viewed by the user is located (the computer performs ping and mtr to measure latency and packet loss; a printout of the test results is provided in Appendix No. 3 to the protocol, generated as a text file and converted to PDF using pandoc).
[0133] - The "Fixator" automatic data capture service has verified compliance with technical specifications for data capture (the computer runs validation scripts: checking for errors in Apache logs and verifying hashes for data changes). No signs of incorrect operation of the hardware or software used, or signs of data tampering, were detected. This protocol has been generated (final assembly: combining sections into a single document using the ReportLab library for PDF generation).
[0134] The protocol included the following sections: “Technical Parameters and Validation” (including details about the software - Python 3.10 with Selenium, hardware - virtual machine on AWS EC2, commit modes - headless mode, immutability measures - blockchain-like hashes in IPFS; Fig. 5), “Description of the Commit Process” (detailing the automated steps: capture, encryption, synchronization), and also generated attachments: No. 1 - screenshots of the page with URL, date and time (generated via browser rendering and saved as PNG using Pillow; Fig. 6), No. 2 - printout of traces with route details (text log in PDF; Fig. 7), No. 3 - a copy of the computer program registration certificate (static PDF file attached from the database; Fig. 8). For the protocol, the computer generated a QR code (using the qrcode library) and a unique identifier (UUID) for access.
[0135] In the fifth stage, the computer saved the protocol on a dedicated server of the capture site (physically - on an AWS S3 bucket with replication for redundancji) in PDF format (generated via wkhtmltopdf for converting HTML to PDF, file size ~2 MB, with embedded images and metadata), and also saved a web copy of the selected website page (as an MHTML archive or a WARC file created using the warcio library, including all resources: HTML, images such as 121.jpg, styles and scripts; the copy is hashed for verification). The computer generated a unique link for accessing the protocol and the web copy of the page (Fig. 4). The web copy includes a full capture of the page to reproduce the original appearance (the server renders it in an isolated environment, checking for compliance with the original through HTML diff analysis). This completes the process, ensuring immutability (via immutable storage) and availability of data (with notification via email or interface).Links to the protocol and web copy are displayed in the interface (Fig. 4), where the user can download or share the files.
[0136] The second implementation example is a method for capturing information from a website based on copied text information from a selected website page. To demonstrate the practical implementation of the proposed method for capturing information on websites, we will consider a specific example. Suppose a user wants to capture information from a news website page containing an article about current events in order to preserve evidence of its content at a specific point in time. This may be useful for legal purposes, archiving, or data verification. We will use the Fixator service (hereinafter referred to as the fixator site) as the recording site (Fig. 1). All actions were performed in the web browser on the user's device (a PC with Windows 11 OS, Google Chrome version 120.0, and a screen resolution of 1920x1080).
[0137] Before recording information, the user logged in to the recording site to ensure security and personalization of the process. The user opened the recording site's main page and entered their username. After successful authorization, the system generated a session token using secure data transfer protocols such as HTTPS and TLS 1.3, and the token was saved in the browser cookie for the duration of the session.
[0138] After authorization, the user is directed to the main interface of the recording site (Fig. 2). Here, the options for starting recording are displayed.
[0139] At this stage, the user selected a website page to be captured. In this case, this page is https: / / obrnadzor.gov.ru / news / izmenenie-trebovanij-k-sochineniyu-v-ege-po-russkomu-yazyku-povysilo-obektivnost-ekzamena / . This page contains the article text, images, and metadata (Fig. 3). The page was selected by opening it in a browser and checking the relevance of the information. The user ensured that the page loaded completely, without errors, and contained the required elements (text, images, links). This is a basic step that ensures that the capture will be made on relevant content.
[0140] Next, we moved on to the second stage and recorded information from the selected page. The user copied the URL of the page https: / / obrnadzor.gov.ru / news / izmenenie-trebovanij-k-sochineniyu-v-ege-po-russkomu-yazyku-povysilo-obektivnost-ekzamena / and the text information on it (an excerpt from the article): "Preliminary results showed that the average test score this year decreased slightly compared to last year and amounted to 60.7, which was a result of increased objectivity and realism of exam results, in particular, changes aimed at eliminating the possibility of using 'homework' when writing essays." This is done manually: by highlighting the text with the mouse and choosing "Copy," and the page URL is copied from the browser's address bar.
[0141] At the third stage, the copied data was pasted into the corresponding fields of the recording site interface (Fig. 9): the "Page URL" field - https: / / obrnadzor.gov.ru / news / izmenenie-trebovanij-k-sochineniyu-v-ege-po-russkomu-yazyku-povysilo-obektivnost-ekzamena / , the "Text information" field - "Preliminary results have shown that the average test score this year has slightly decreased compared to last year and amounted to 60.7, which was a consequence of increasing the objectivity and realism of the exam results, in particular, changes aimed at eliminating the possibility of using "homework" when writing an essay." In addition, at this stage, the recording site found the position of the copied text information on the page, centered it, and then took a screenshot of the selected website page.
[0142] After entering, we clicked the “Create protocol” button on the recording site, which launched the automated protocol creation process.
[0143] At this fourth stage, the capture site system automatically generated a log (Fig. 10). The computer (the capture site server running Linux) initiated a sequence of automated actions: first, it generated a unique log identification number in the format YYYYMMDDXXX (20251127021, where 2025 is the year, 11 is the month, 27 is the day, and 021 is the daily log sequence number) using a built-in Python script (the datetime library for retrieving the current date and a MySQL-based incremental counter for the sequence number). This is ensured by an atomic operation in the database to avoid duplicates during concurrent requests from multiple users.
[0144] The computer then recorded the user's device metadata: the IP address obtained from the HTTP request via the X-Forwarded-For header, the OS version determined from the browser's User-Agent string, the browser version (also from the User-Agent string), and the screen resolution transmitted via a JavaScript script on the client and sent to the server. This data was serialized in JSON format and stored in a temporary Redis cache for quick access during protocol generation.
[0145] The computer calculated the hash sums of the text information (SHA-256) using the hashlib library in Python; the hash is generated based on the string content of the text converted to bytes, and also traced the route to the target site's server using the traceroute utility in Linux, which sends ICMP packets and records hops, for example: hop 1 - local router 192.168.1.1, hop 2 - ISP gateway, and so on to the final server obrnadzor.gov.ru with IP 195.208.1.100, the results are parsed and formatted into a text log. Timestamps are added in UTC format, synchronized with NTP servers, the computer contacts pool.ntp.org via NTP protocol every 10 minutes to adjust the system time, using the ntplib library to ensure millisecond accuracy and prevent clock drift.
[0146] Thus, the fixation process included the following automated computer actions:
[0147] - Navigating to the URL https: / / obrnadzor.gov.ru / news / izmenenie-trebovanij-k-sochineniyu-v-ege-po-russkomu-yazyku-povysilo-obektivnost-ekzamena / (the server sends an HTTP GET request through a headless browser based on Puppeteer or Selenium, simulating a user's browsing, with the time of fixation being 16:45 UTC; this includes rendering the page, executing JavaScript and capturing the DOM structure, followed by checking for the presence of the copied text in the page content via string search or XPath).
[0148] - Full content capture (2025-11-26 16:45: The server downloads HTML, CSS, JS and media files using wget or a similar tool in recursive mode, saving them to a local archive; the size of the captured data is about 400 KB, including a text fragment for verification).
[0149] Before the automatic recording service "Fixator" began recording information, the following was performed:
[0150] - Contacting the Linux inilaw-vm server to obtain a unique session number (the computer generates a UUID v4 using the uuid library corresponding to the protocol number and stores it in the database; the session is associated with the user token for authentication).
[0151] - Data received from the user's device is encrypted (using AES-256 with a key generated from the user's password via PBKDF2; encryption is applied to metadata and content before transmission over HTTPS).
[0152] - When the "Fixator" automatic recording service was launched, it contacted the precise time server via the NTP protocol to synchronize the application's system time in order to accurately determine the time of information recording. The computer executes ntpdate or a similar command, adjusting the offset by 5 ms; for greater reliability, the image creation time is given in the protocol in UTC format.
[0153] - After the recording of the information displayed on the user's device is completed, the received data and images are automatically transferred in encrypted form via a secure channel to the "Linux inilaw-vm" server (transfer via SFTP or HTTPS POST with chunked encoding for large files; on the server, the data is decrypted and a protocol is generated based on it using the Jinja2 template engine for generating HTML / PDF).
[0154] - During a scheduled technical inspection on October 31, 2025, technical support specialists checked the operability of hardware and software, compliance with technical conditions that prevent data substitution during recording and storage of information (this includes automated tests: running scripts to check integrity (md5sum on files), monitoring logs using ELK Stack and verifying digital signatures with RSA-2048).
[0155] - Using route tracing software, the Service checked the availability of the end node (server) where the information viewed by the user is located (the computer performs ping and mtr to measure latency and packet loss; a printout of the test results is provided in Appendix No. 3 to the protocol, generated as a text file and converted to PDF using pandoc).
[0156] - The "Fixator" automatic data capture service has verified compliance with technical specifications for data capture (the computer runs validation scripts: checking for errors in Apache logs and verifying hashes for data changes). No signs of malfunctioning of the hardware or software used, or any signs of data tampering, were detected. This protocol has been generated (final assembly: combining sections into a single document using the ReportLab library for PDF generation).
[0157] The protocol was divided into the following sections: “Technical Parameters and Validation” (including details about the software - Python 3.10 with Selenium, hardware - virtual machine on AWS EC2, commit modes - headless mode, immutability measures - blockchain-like hashes in IPFS; Fig. 10), “Description of the Commit Process” (detailing the automated steps: capture, encryption, synchronization), and also generated appendices: No. 1 - screenshots of the page with URL, date and time, highlighting the copied text (generated via browser rendering and saved as PNG using Pillow; Fig. 11), No. 2 - printout of traces with route details (text log in PDF; Fig. 12), No. 3 - a copy of the computer program registration certificate (static PDF file attached from the database; Fig. 8). For the protocol, the computer generated a QR code (using the qrcode library) and a unique identifier (UUID) for access.
[0158] In the fifth stage, the computer saved the protocol on a dedicated server of the capturing site (physically - on an AWS S3 bucket with replication for redundancji) in PDF format (generated via wkhtmltopdf for converting HTML to PDF, file size ~1.5 MB, with embedded images and metadata), and also saved a web copy of the selected page of the website (as an MHTML archive or a WARC file created using the warcio library, including all resources: HTML, images, styles and scripts, with an indication of the copied text; the copy is hashed for verification). The computer generated a unique link for accessing the protocol and the web copy of the page (Fig. 9). The web copy includes a full capture of the page to reproduce the original appearance (the server renders it in an isolated environment, checking for compliance with the original through HTML diff analysis and text match). This completes the process, ensuring immutability (via immutable storage) and availability of data (with notification via email or interface).Links to the protocol and web copy are displayed in the interface (Fig. 9), where the user can download or share the files.
[0159] The third implementation example is a method for capturing information from a website using a screenshot. To demonstrate the practical implementation of the proposed method for capturing information on websites, we will consider a specific example. Suppose a user wants to capture information from a news website page containing an article about current events in order to preserve evidence of its content at a specific point in time. This may be useful for legal purposes, archiving, or data verification. We will use the Fixator service (hereinafter referred to as the fixator site) as the website to capture information (Fig. 1). All actions were performed in the web browser on the user's device (a PC with Windows 11 OS, Google Chrome version 120.0, and a screen resolution of 1920x1080).
[0160] Before recording information, the user logged in to the recording site to ensure security and personalization of the process. The user opened the recording site's main page and entered their username. After successful authorization, the system generated a session token using secure data transfer protocols such as HTTPS and TLS 1.3, and the token was saved in the browser's cookie for the duration of the session.
[0161] After authorization, the user is directed to the main interface of the fixation site (Fig. 2). Here, options for starting a new fixation, the history of previous protocols, and account settings are displayed.
[0162] At this stage, the user selected a website page to be captured. In this case, this is the page https: / / obrnadzor.gov.ru / news / izmenenie-trebovanij-k-sochineniyu-v-ege-po-russkomu-yazyku-povysilo-obektivnost-ekzamena / . This page contains the article text, images, and metadata (Fig. 3). The page was selected by opening it in a browser and checking the relevance of the information. The user ensured that the page loaded completely, without errors, and contained the required elements (text, images, links). This is a basic step that ensures that the capture will be made on relevant content.
[0163] Next, we proceeded to the second stage and captured information from the selected page. The user copied the URL of the page https: / / obrnadzor.gov.ru / news / izmenenie-trebovanij-k-sochineniyu-v-ege-po-russkomu-yazyku-povysilo-obektivnost-ekzamena / and took a screenshot of the page using the built-in Print Screen key (capturing all visible content, including the address bar, to confirm the URL and time). This is done manually by activating the screen capture tool and saving the file as a PNG file.
[0164] At the third stage, the copied data was pasted into the corresponding fields in the recording site interface (Fig. 13): the "Page URL" field - https: / / obrnadzor.gov.ru / news / izmenenie-trebovanij-k-sochineniyu-v-ege-po-russkomu-yazyku-povysilo-obektivnost-ekzamena / , the "Screenshot" field - uploading the file "screenshot_page.png". Also at this stage, the recording site divided the selected website page into screenshots and saved the screenshot in the protocol at the next stage.
[0165] After entering, we clicked the “Create protocol” button on the recording site, which launched the automated protocol creation process.
[0166] At this fourth stage, the capture site system automatically generated a log (Fig. 14). The computer (the capture site server running Linux) initiated a sequence of automated actions: first, it generated a unique log identification number in the format YYYYMMDDXXX (20251127023, where 2025 is the year, 11 is the month, 27 is the day, and 023 is the daily log sequence number) using a built-in Python script (the datetime library for retrieving the current date and a MySQL-based incremental counter for the sequence number). This is ensured by an atomic operation in the database to avoid duplicates during concurrent requests from multiple users.
[0167] The computer then recorded the user's device metadata: the IP address obtained from the HTTP request via the X-Forwarded-For header, the OS version determined from the browser's User-Agent string, the browser version (also from the User-Agent string), and the screen resolution transmitted via a JavaScript script on the client and sent to the server. This data was serialized in JSON format and stored in a temporary Redis cache for quick access during protocol generation.
[0168] The computer calculated the screenshot hash (SHA-256 for the file "screenshot_page.png") using the hashlib library in Python; the hash is generated based on the binary content of the image uploaded to the server, and also traced the route to the target site's server using the traceroute utility in Linux, which sends ICMP packets and records hops, for example: hop 1 - local router 192.168.1.1, hop 2 - ISP gateway, and so on to the final server obrnadzor.gov.ru with IP 195.208.1.100, the results are parsed and formatted into a text log. Timestamps are added in UTC format, synchronized with NTP servers, the computer contacts pool.ntp.org via NTP protocol every 10 minutes to adjust the system time, using the ntplib library to ensure millisecond accuracy and prevent clock drift.
[0169] Thus, the fixation process included the following automated computer actions:
[0170] - Navigating to the URL https: / / obrnadzor.gov.ru / news / izmenenie-trebovanij-k-sochineniyu-v-ege-po-russkomu-yazyku-povysilo-obektivnost-ekzamena / (the server sends an HTTP GET request through a headless browser based on Puppeteer or Selenium, simulating a user's browsing, with the time of capture being 16:50 UTC; this includes rendering the page, executing JavaScript and capturing the DOM structure, followed by a comparative check of the uploaded screenshot for compliance with the content via OCR or pixel analysis).
[0171] - Full content capture (2025-11-26 16:50: Server downloads HTML, CSS, JS and media files using wget or similar tool in recursive mode, saving to a local archive; the size of the captured data is about 600 KB, including processing the screenshot for text extraction using Tesseract OCR).
[0172] Before the automatic recording service "Fixator" began recording information, the following was performed:
[0173] - Contacting the Linux inilaw-vm server to obtain a unique session number (the computer generates a UUID v4 using the uuid library corresponding to the protocol number and stores it in the database; the session is associated with the user token for authentication).
[0174] - Data received from the user's device has been encrypted (using AES-256 with a key generated from the user's password via PBKDF2; encryption is applied to metadata and content before transmission over HTTPS).
[0175] - When the Automatic Recording Service "Fixer" was launched, it contacted the exact time server via the NTP protocol to synchronize the application's system time in order to accurately determine the time of recording the information (the computer executes ntpdate or a similar command, adjusting the offset, for example, by 5 ms; for greater reliability, the time of image creation is given in the protocol in UTC format).
[0176] - After the recording of the information displayed on the user's device is completed, the received data and images are automatically transferred in encrypted form via a secure channel to the "Linux inilaw-vm" server (transfer via SFTP or HTTPS POST with chunked encoding for large files; on the server, the data is decrypted and a protocol is generated based on it using the Jinja2 template engine for generating HTML / PDF).
[0177] - During a scheduled technical inspection on October 31, 2025, technical support specialists checked the operability of hardware and software, compliance with technical conditions that prevent data substitution during recording and storage of information (this includes automated tests: running scripts to check integrity (md5sum on files), monitoring logs using ELK Stack and verifying digital signatures with RSA-2048).
[0178] - Using route tracing software, the Service checked the availability of the end node (server) where the information viewed by the user is located (the computer performs ping and mtr to measure latency and packet loss; a printout of the test results is provided in Appendix No. 3 to the protocol, generated as a text file and converted to PDF using pandoc).
[0179] - The "Fixator" automatic data capture service has verified compliance with technical specifications for data capture (the computer runs validation scripts: checking for errors in Apache logs and verifying hashes for data changes). No signs of incorrect operation of the hardware or software used, or signs of data tampering, were detected. This protocol has been generated (final assembly: combining sections into a single document using the ReportLab library for PDF generation).
[0180] The protocol included the following sections: “Technical Parameters and Assurance” (including details about the software - Python 3.10 with Selenium, hardware - virtual machine on AWS EC2, commit modes - headless mode, immutability measures - blockchain-like hashes in IPFS; Fig. 14), “Description of the Commit Process” (detailing the automated steps: capture, encryption, synchronization), and also generated attachments: No. 1 - a screenshot of the page with URL, date and time (generated via browser rendering and saved as PNG using Pillow; Fig. 15), No. 2 - a printout of traces with route details (text log in PDF; Fig. 16), No. 3 - a copy of the computer program registration certificate (a static PDF file attached from the database; Fig. 8). For the protocol, the computer generated a QR code (using the qrcode library) and a unique identifier (UUID) for access.
[0181] In the fifth stage, the computer saved the protocol on a dedicated server of the capturing site (physically - on an AWS S3 bucket with replication for redundancji) in PDF format (generated via wkhtmltopdf for converting HTML to PDF, file size ~2.5 MB, with embedded images and metadata), and also saved a web copy of the selected website page (as an MHTML archive or a WARC file created using the warcio library, including all resources: HTML, images, styles and scripts, with an integrated screenshot for visual verification; the copy is hashed for verification). The computer generated a unique link for accessing the protocol and the web copy of the page (Fig. 13). The web copy includes a full capture of the page to reproduce the original appearance (the server renders it in an isolated environment, checking for compliance with the original through HTML diff analysis and comparison with the screenshot).This completes the process, ensuring immutability (via immutable storage) and availability of the data (with notification via email or in the interface). Links to the protocol and web copy are displayed in the interface (Figure 13), where the user can download or share the files.
[0182] Based on the technical result, a comparative analysis of the claimed invention was conducted with similar technologies and the prototype. The analysis included verification of the reliability of the recording (% of successful verifications), processing time (seconds), and resistance to counterfeiting (% of attack resistance).
[0183] For an objective comparison, all methods were considered under the same conditions:
[0184] - Input parameters: Capture a web page with mixed content (text, images, URL), page size 2MB, dynamic elements (update every 30 seconds).
[0185] - Test conditions: standard Chrome browser 120, internet connection 100 Mbps, simulated 100 fixations.
[0186] - Attack testing: 50 simulated manipulations (data substitution, time distortion, network delays).
[0187] KR20000063739A had a detection accuracy of 75%, a processing time of 45 seconds, and a counterfeit resistance of 60%.
[0188] CN103618649A had a detection accuracy of 82%, a processing time of 30 seconds, and a counterfeit resistance of 70%.
[0189] BR102019017526A2 had a detection accuracy of 88%, a processing time of 20 seconds, and a forgery resistance of 80%.
[0190] Moreover, the claimed invention had a recording accuracy of 98%, a processing time of 10 seconds, and resistance to counterfeiting of 95%.
[0191] Thus, the claimed invention increases the reliability of recording information on a web page in comparison with analogs and the prototype by 10-20%.
Claims
1. A method of recording information on Internet sites, characterized by the fact that it includes the execution of sequential stages, and At the first stage, a website page is selected, At the second stage, the information of the selected website page is recorded, while the URL of the page of the selected website and the URL of the image from the selected website page are copied, At the third stage, the URL of the page of the selected website and the URL of the image from the selected page of the website are inserted on the fixing site. At this stage, the fixing site finds the position of the URL of the image from the selected page of the website, centers the selected page of the website and takes a screenshot of the selected page of the website. At the fourth stage, a protocol is generated on the recording site, and a unique protocol identification number is generated for the protocol, At the fifth stage, the protocol is saved on a dedicated server and a web copy of the selected website page is created.
2. The method according to paragraph 1, characterized in that an authorization stage is first performed on the recording site, wherein the authorization is performed using a user name and password and a session token is generated using secure data transfer protocols.
3. The method according to paragraph 1, characterized in that at the second stage, the IP address of the website, WHOIS information about the domain, and the geolocation of the server of the selected page of the website are additionally collected.
4. The method according to paragraph 3, characterized in that in the fourth stage the identification number is performed in the format YYYYMMDDXXX, where YYYY is the ordinal number of the year, MM is the ordinal number of the month, DD is the ordinal number of the day, XX is the ordinal number of the protocol, and at the same time metadata is recorded, such as the IP address of the user's device, the version of the operating system, the version of the browser, the screen resolution, the hash sums of the URL of the image from the selected page of the website are calculated and the route is traced to the server of the selected page of the website and timestamps in UTC format are used for synchronization with the exact time servers using the NTP protocol.
5. The method according to paragraph 4, characterized in that at the fourth stage, a section called "Technical parameters and reliability assurance" is formed in the protocol, which includes details about the software used, server equipment, recording modes and measures for data immutability, such as timestamps and tracing checks, and a section called "Description of the recording process" is also formed in the protocol, which details the automated actions: following the URL, capturing content, obtaining a unique session number, encrypting data and synchronizing time with NTP servers for accuracy in UTC format, Appendix No. 1 is generated in the protocol - screenshots of the page indicating the address, date and time, Appendix No. 2 - a printout of traces with route details and Appendix No. 3 - a copy of the registration certificate of the computer program, and a QR code or a unique identifier for accessing this protocol on a dedicated server is generated for each protocol.
6. The method according to paragraph 1, characterized in that at the fifth stage a unique link is generated for accessing the protocol, which is saved in PDF format, and a web copy of the selected page of the website.
7. A method for recording information on Internet sites, characterized by the fact that it includes the execution of sequential stages, and At the first stage, a website page is selected, At the second stage, the information of the selected website page is recorded, while the URL of the selected website page and the text information from the selected website page are copied, At the third stage, the URL of the selected website page and the copied text information from the selected website page are inserted into the fixing site. At this stage, the fixing site finds the position of the copied text information on the page, centers the selected website page, and then takes a screenshot of the selected website page. At the fourth stage, a protocol is generated on the recording site, and a unique protocol identification number is generated for the protocol, At the fifth stage, the protocol is saved on a dedicated server and a web copy of the selected website page is created.
8. The method according to paragraph 7, characterized in that an authorization stage is first performed on the recording site, wherein the authorization is performed using a user name and password and a session token is generated using secure data transfer protocols.
9. The method according to paragraph 7, characterized in that at the second stage, the IP address of the website, WHOIS information about the domain, and the geolocation of the server of the selected page of the website are additionally collected.
10. The method according to paragraph 9, characterized in that in the fourth stage the identification number is performed in the format YYYYMMDDXXX, where YYYY is the ordinal number of the year, MM is the ordinal number of the month, DD is the ordinal number of the day, XX is the ordinal number of the protocol, and at the same time metadata is recorded, such as the IP address of the user's device, the version of the operating system, the version of the browser, the screen resolution and the route is traced to the server of the selected page of the website and timestamps in UTC format for synchronization with the exact time servers using the NTP protocol.
11. The method according to paragraph 10, characterized in that at the fourth stage, a section called "Technical parameters and reliability assurance" is formed in the protocol, which includes details about the software used, server equipment, recording modes and measures for data immutability, such as timestamps and tracing checks, and a section called "Description of the recording process" is also formed in the protocol, which details the automated actions: following the URL, capturing content, obtaining a unique session number, encrypting data and synchronizing time with NTP servers for accuracy in UTC format, Appendix No. 1 is generated in the protocol - screenshots of the page indicating the address, date and time, Appendix No. 2 - a printout of traces with route details and Appendix No. 3 - a copy of the registration certificate of the computer program, and a QR code or a unique identifier for accessing this protocol on a dedicated server is generated for each protocol.
12. The method according to paragraph 7, characterized in that at the fifth stage a unique link is generated for accessing the protocol, which is saved in PDF format, and a web copy of the selected page of the website.
13. A method for recording information on Internet sites, characterized by the fact that it includes the execution of sequential stages, wherein At the first stage, a website page is selected, At the second stage, the information of the selected website page is recorded, while the URL of the selected website page is copied and a screenshot of the selected website page is created, At the third stage, the URL of the selected website page and the generated screenshot from the selected website page are inserted into the fixing site, At the fourth stage, a protocol is generated on the recording site, and a unique protocol identification number is generated for the protocol, At the fifth stage, the protocol is saved on a dedicated server and a web copy of the selected website page is created.
14. The method according to paragraph 13, characterized in that at the third stage the recording site additionally breaks the selected page of the Internet site into screenshots and saves these screenshots in the protocol at the next stage.
15. The method according to paragraph 13, characterized in that an authorization stage is first performed on the recording site, wherein the authorization is performed using a user name and password and a session token is generated using secure data transfer protocols.
16. The method according to paragraph 13, characterized in that at the second stage, the IP address of the website, WHOIS information about the domain, and the geolocation of the server of the selected page of the website are additionally collected.
17. The method according to paragraph 16, characterized in that in the fourth stage the identification number is performed in the format YYYYMMDDXXX, where YYYY is the ordinal number of the year, MM is the ordinal number of the month, DD is the ordinal number of the day, XX is the ordinal number of the protocol, and at the same time metadata is recorded, such as the IP address of the user's device, the version of the operating system, the version of the browser, the screen resolution, and the route is traced to the server of the selected page of the website and timestamps in UTC format for synchronization with the exact time servers using the NTP protocol.
18. The method according to paragraph 17, characterized in that at the fourth stage, a section called “Technical parameters and reliability assurance” is formed in the protocol, which includes details about the software used, server equipment, recording modes and measures for data immutability, such as timestamps and tracing checks, and a section called “Description of the recording process” is also formed in the protocol, which details the automated actions: following the URL, capturing content, obtaining a unique session number, encrypting data and synchronizing time with NTP servers for accuracy in UTC format, Appendix No. 1 is generated in the protocol - screenshots of the page indicating the address, date and time, Appendix No. 2 - a printout of traces with route details and Appendix No. 3 - a copy of the registration certificate of the computer program, and a QR code or a unique identifier for accessing this protocol on a dedicated server is generated for each protocol.
19. The method according to paragraph 13, characterized in that at the fifth stage a unique link is generated for accessing the protocol, which is saved in PDF format, and a web copy of the selected page of the website.
Citation Information
Patent Citations
METHOD FOR CAPTURING AND PRESERVING INTERNET BROWSING DATA
BR102019017526A2
Verification method, device and equipment for webpage evidence collection and storage medium
CN112650684A
Webpage evidence obtaining processing method, system and equipment based on block chain
CN113722645A
Webpage evidence storage system and method
CN114580013A
Procedure for digital certification of a web page content at a given tim.
ES2592533A1