Loaded from cache (as of 2026-07-08 05:03:17 IST). Refresh
Intelligence Report for bigcom.ru
| Domain | bigcom.ru |
|---|---|
| Website Title |  BIG COMPANY |
| Registered | N/A |
| Expires | N/A |
| Remaining Validity | N/A |
| Domain Age | N/A |
| Registrar | N/A |
| Domain Status | N/A |
| IP Address | 188.120.239.56 |
| Hosting Provider | JSC IOT |
| Control Panel | Not Detected |
| Email Provider | Self-hosted or Custom |
| SSL Issuer | GlobalSign GCC R6 AlphaSSL CA 2025 |
| SSL Issued Date | 2025-12-15 |
| SSL Expires | 2027-01-16 |
Domain Information
Registrar Information
Registrant Contact
Contact information for this role is not provided or redacted.
Administrative Contact
Contact information for this role is not provided or redacted.
Technical Contact
Contact information for this role is not provided or redacted.
NS Records
| Name | Data |
|---|---|
| bigcom.ru. | ns4-cloud.nic.ru. |
| bigcom.ru. | ns3-l2.nic.ru. |
| bigcom.ru. | ns4-l2.nic.ru. |
| bigcom.ru. | ns8-l2.nic.ru. |
| bigcom.ru. | ns8-cloud.nic.ru. |
A Records
| Name | Data |
|---|---|
| bigcom.ru. | 188.120.239.56 |
AAAA Records
No AAAA records found.
WWW Records (www.bigcom.ru)
| Type | Host | Value |
|---|---|---|
| A | www.bigcom.ru. | 188.120.239.56 |
MX Records
| Priority | Target |
|---|---|
| 5 | post.bigcom.ru. |
TXT Records
| Name | Data |
|---|---|
| bigcom.ru. | google-site-verification=uo4z9UIPrWEA5KOr2LaE2F-X4XcGDSC_FDZgxBvhpaU |
| bigcom.ru. | v=spf1 mx ~all |
IP Address Details
| IP Address | 188.120.239.56 |
|---|---|
| Country | Russia (RU) |
| Region | Moscow Oblast |
| City | Novoivanovskoye |
| ZIP Code | 664017 |
| ASN | 29182 |
| Organization | JSC IOT |
SPF Record Validation
v=spf1 mx ~all
Record Breakdown
| Prefix | Type | Value | Description |
|---|---|---|---|
| + | v | spf1 | The SPF record version. |
| + | mx | Match if the sender's IP is one of the domain's MX records. | |
| ~ | all | Always matches. This should be the last mechanism. |
Validation Summary
| SPF Record Published | Pass An SPF record was found. |
| Multiple SPF Records | Pass Only one SPF record was found. |
| Included Lookups | Pass The number of DNS lookups (1) is within the limit of 10. |
| Type PTR Check | Pass The deprecated PTR mechanism was not found. |
| Characters After ALL | Pass No mechanisms were found after the "all" mechanism. |
Common DKIM Records
No common DKIM selectors found. Custom selectors may be in use.
DMARC Record Validation
v=DMARC1; p=quarantine
Record Breakdown
| Tag | Value | Description |
|---|---|---|
| v | DMARC1 | Version: Must be "DMARC1". |
| p | quarantine | Policy: The action to take for failed emails (none, quarantine, reject). |
Validation Summary
| DMARC Record Published | Pass A DMARC record was found. |
| Syntax Check | Pass The record has a valid version tag. |
| Policy Enforcement | Pass The policy is "p=quarantine", which sends failing emails to spam. |
| Aggregate Reporting | Warning No "rua" tag was found. You will not receive summary reports. |
Suggestions
This is a good step. Continue monitoring reports and consider moving to "p=reject" for the highest level of protection.
It is highly recommended to add an "rua" tag (e.g., "rua=mailto:dmarc-reports@yourdomain.com") to monitor email traffic and ensure legitimate emails are not failing checks.
SMTP Connectivity Test (Port 25)
| Mail Server | Status | Latency | Banner / Error |
|---|---|---|---|
| post.bigcom.ru | Success | 469ms | 220 post.bigcom.ru ESMTP Wed, 08 Jul 2026 02:33:17 +0300 |
IP Blacklist Check (188.120.239.56)
Website Identity
| Title | BIG COMPANY |
|---|---|
| Meta Description | N/A |
Hosting & Network
| IP Address | 188.120.239.56 |
|---|---|
| HTTP Status | 200 |
| Hosting Provider | JSC IOT |
| Web Server | Apache/2.4.6 (CentOS) mpm-itk/2.4.7-04 OpenSSL/1.0.2k-fips mod_fcgid/2.3.9 PHP/8.3.22 |
| Control Panel | Not Detected |
Technology Profile
- Apache
- PHP
- Google Fonts
SSL Certificate Details
- Server IP address : 188.120.239.56
- Server Type : Apache/2.4.6 (CentOS) mpm-itk/2.4.7-04 OpenSSL/1.0.2k-fips mod_fcgid/2.3.9 PHP/8.3.22
- Issuer : GlobalSign GCC R6 AlphaSSL CA 2025
- Expiring In : 192 Days
- Chain Status: Valid
- Common name : *.bigcom.ru
- Alternative names (SANs) : DNS:*.bigcom.ru, DNS:bigcom.ru
- Organization: N/A
- Valid From Dec 15, 2025 to Jan 16, 2027
- Signature Algorithm : RSA-SHA256
- Issuer : GlobalSign GCC R6 AlphaSSL CA 2025
- Common name : GlobalSign GCC R6 AlphaSSL CA 2025
- Organization : GlobalSign nv-sa
- Valid From May 21, 2025 to May 21, 2027
- Signature Algorithm : RSA-SHA256
- Issuer : GlobalSign
- Common name : GlobalSign
- Organization : GlobalSign
- Valid From Dec 10, 2014 to Dec 10, 2034
- Signature Algorithm : RSA-SHA384
- Issuer : GlobalSign
Security Headers
| Strict-Transport-Security | Present |
| Content-Security-Policy | Missing |
| X-Frame-Options | Missing |
| X-Content-Type-Options | Missing |
| Referrer-Policy | Missing |
| Permissions-Policy | Missing |
Understanding Your Report for bigcom.ru
Domain Status
Also known as EPP status codes, these indicate the state of the domain. Common statuses include 'clientTransferProhibited' (locked) or 'active' (ready to use).
Registrar Information
The registrar is the accredited organization (like GoDaddy, Namecheap, or Google Domains) where the domain name was purchased and is managed.
Registrant Contact
The individual or organization that legally owns the domain. This information is often redacted for privacy compliance (GDPR).
Nameservers
Servers that act as a directory for your domain. They translate your domain name into IP addresses, telling the internet where to find your website and email services.
NS Records
Name Server records specify which nameservers are authoritative for your domain. Changing these allows you to move DNS management to a different provider.
A Records
Address Records map a domain name directly to an IPv4 address (e.g., 192.0.2.1). This is the primary record used to point a domain to a web server.
AAAA Records
IPv6 Address Records map a domain name to an IPv6 address (e.g., 2001:0db8...). They serve the same purpose as A records but for the newer internet protocol.
WWW Records
Usually a CNAME or A record that ensures 'www.yourdomain.com' loads the same content as the root domain 'yourdomain.com'.
MX Records
Mail Exchange records direct emails sent to your domain to the correct mail servers. Without valid MX records, you cannot receive email.
TXT Records
Text records allow admins to store text notes in the DNS. They are primarily used for domain verification and email security protocols like SPF and DKIM.
SPF Records
Sender Policy Framework is a security record listing the IP addresses and servers authorized to send email on behalf of your domain to prevent spoofing.
DMARC Records
Domain-based Message Authentication, Reporting, and Conformance uses SPF and DKIM to determine email authenticity and instructs receivers how to handle failed checks.
DKIM Records
DomainKeys Identified Mail stores a public key in the DNS. Receivers use this to verify the digital signature on your emails, ensuring they haven't been tampered with.
HTTP Status
A 3-digit code returned by the server indicating the result of a request (e.g., 200 OK, 301 Redirect, 404 Not Found, 500 Server Error).
Hosting Provider
The company providing the physical or virtual servers where your website's files, databases, and content are stored and served to the internet.
Web Server
The software (like Apache, Nginx, or LiteSpeed) running on the hosting server that handles incoming requests and delivers web pages to visitors.
Control Panel
The interface provided by your host (e.g., cPanel, Plesk, DirectAdmin) to manage your website files, databases, email accounts, and settings.
Technology Profile
Detects the underlying software stack used by the website, including Content Management Systems (CMS), JavaScript frameworks, programming languages, and analytics tools.
Report Limitations & Data Sources
- Data Currency: This report may use cached data (up to 4 hours) for speed. Use the "Refresh" button to force a live lookup.
- DNS Propagation: Records are queried via Google Public DNS. Recently changed records might not be visible immediately due to global propagation delays.
- Completeness: This tool checks for specific, common DNS records (A, MX, TXT, etc.). It does not perform a full zone transfer or exhaustive subdomain enumeration.
- Security Posture: The security analysis (SPF/DMARC) is based on public DNS availability. It cannot verify internal mail server configurations, firewalls, or email filtering rules.