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



X

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

Checked:
14.09.2021 22:54:38


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
1c.argasmo.ru
A
185.134.232.34
Krasnodar/Krasnodarskiy Kray/Russia (RU) - Petrenko's network
No Hostname found
yes
1
0

AAAA

yes


www.1c.argasmo.ru

Name Error
yes
1
0
*.argasmo.ru
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.1c.argasmo.ru
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

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



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



Status: Valid because published



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 26838, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



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



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

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



DS with Algorithm 8, KeyTag 7729, DigestType 2 and Digest wDWHERO7fHDB+/wcm/36l4FzM0jVT375pK0CGqADNvM=



1 RRSIG RR to validate DS RR found



RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.09.2021, 17:00:00 +, Signature-Inception: 14.09.2021, 16:00:00 +, KeyTag 26838, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 51699, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 345600 sec, Signature-expiration: 02.10.2021, 00:00:00 +, Signature-Inception: 12.09.2021, 00:00:00 +, KeyTag 7729, Signer-Name: ru



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 7729, DigestType 2 and Digest "wDWHERO7fHDB+/wcm/36l4FzM0jVT375pK0CGqADNvM=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

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



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "nivihd5abg760f24affudf3kt7b1u1a3" between the hashed NSEC3-owner "niua7vejultm1h822m6v30adco1q2jqa" and the hashed NextOwner "nj3gkjgb4ikjij2uvhvqht7bg6a93j5l". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner niua7vejultm1h822m6v30adco1q2jqa.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 14.10.2021, 21:37:53 +, Signature-Inception: 03.09.2021, 12:16:50 +, KeyTag 51699, Signer-Name: ru



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "tdui9d4jkuds8b9t86gj39pgflcnlgm5" as Owner. That's the Hash of "ru" with the NextHashedOwnerName "te33kgtaqu9m5crq3ibsilqu11gfgttt". So that domain name is the Closest Encloser of "argasmo.ru". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner tdui9d4jkuds8b9t86gj39pgflcnlgm5.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 17.10.2021, 10:26:34 +, Signature-Inception: 03.09.2021, 12:16:50 +, KeyTag 51699, Signer-Name: ru



0 DNSKEY RR found




Zone: 1c.argasmo.ru
1c.argasmo.ru
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.1c.argasmo.ru
www.1c.argasmo.ru
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.1c.argasmo.ru
  ns1.beget.com

1c.argasmo.ru
  ns1.beget.com
5.101.159.11
St Petersburg/St.-Petersburg/Russia (RU) - Geo location BEGET.RU

argasmo.ru
  ns1.beget.com
5.101.159.11
St Petersburg/St.-Petersburg/Russia (RU) - Geo location BEGET.RU


  ns1.beget.pro
5.101.159.11
St Petersburg/St.-Petersburg/Russia (RU) - Geo location BEGET.RU


  ns1.beget.ru
5.101.159.11
St Petersburg/St.-Petersburg/Russia (RU) - Geo location BEGET.RU


  ns2.beget.com
185.50.27.12
St Petersburg/St.-Petersburg/Russia (RU) - Beget LLC


  ns2.beget.pro
185.50.27.12
St Petersburg/St.-Petersburg/Russia (RU) - Beget LLC


  ns2.beget.ru
185.50.27.12
St Petersburg/St.-Petersburg/Russia (RU) - Beget LLC

ru
  a.dns.ripn.net / tau.ripn.net


  b.dns.ripn.net


  d.dns.ripn.net / gamma2-nsk.ripn.net


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


  f.dns.ripn.net / tau-sin.ripn.net


4. SOA-Entries


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


Domain:argasmo.ru
Zone-Name:argasmo.ru
Primary:ns1.beget.com
Mail:hostmaster.beget.com
Serial:1616767213
Refresh:300
Retry:600
Expire:86400
TTL:300
num Entries:6


Domain:1c.argasmo.ru
Zone-Name:argasmo.ru
Primary:ns1.beget.com
Mail:hostmaster.beget.com
Serial:1616767213
Refresh:300
Retry:600
Expire:86400
TTL:300
num Entries:1


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


5. Screenshots

Startaddress: https://1c.argasmo.ru, address used: https://1c.argasmo.ru/, Screenshot created 2021-09-14 22:56:16 +00:0 url is insecure, certificate invalid

Mobil (412px x 732px)

159 milliseconds

Screenshot mobile - https://1c.argasmo.ru/
Mobil + Landscape (732px x 412px)

151 milliseconds

Screenshot mobile landscape - https://1c.argasmo.ru/
Screen (1280px x 1680px)

464 milliseconds

Screenshot Desktop - https://1c.argasmo.ru/

Mobile- and other Chrome-Checks

widthheight
visual Viewport412732
content Size412732

Good: No horizontal scrollbar. Content-size width = visual Viewport width.

Chrome-Connection: secure. secure connection settings. The connection to this site is encrypted and authenticated using TLS 1.2, ECDHE_RSA with P-384, and AES_256_GCM.

Chrome-Resources : secure. all served securely. All resources on this page are served securely.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://1c.argasmo.ru/
185.134.232.34
-14

10.044
T
Timeout - The operation has timed out

• https://1c.argasmo.ru/
185.134.232.34
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 103.96 %
3.123
N
Not Found
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
small visible content (num chars: 162)
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd"> Not Found Not Found HTTP Error 404. The requested resource is not found.
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Tue, 14 Sep 2021 20:55:37 GMT
Connection: close
Content-Length: 315

• http://1c.argasmo.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
185.134.232.34
-14

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

• https://185.134.232.34/
185.134.232.34
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 103.96 %
3.094
N
Not Found
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
small visible content (num chars: 162)
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd"> Not Found Not Found HTTP Error 404. The requested resource is not found.
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Tue, 14 Sep 2021 20:55:52 GMT
Connection: close
Content-Length: 315

7. Comments


1. General Results, most used to calculate the result

Aname "1c.argasmo.ru" is subdomain, public suffix is ".ru", top-level-domain is ".ru", top-level-domain-type is "country-code", Country is Russian Federation (the), tld-manager is "Coordination Center for TLD RU", num .ru-domains preloaded: 1803 (complete: 168171)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: 1c.argasmo.ru has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: 1c.argasmo.ru has no ipv6 address.
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Bhttps://1c.argasmo.ru/ 185.134.232.34
404

Missing HSTS-Header
CError - no version with Http-Status 200
Hfatal error: No https - result with http-status 200, no encryption
Mhttps://1c.argasmo.ru/ 185.134.232.34
404

Misconfiguration - main pages should never send http status 400 - 499
Mhttps://185.134.232.34/ 185.134.232.34
404

Misconfiguration - main pages should never send http status 400 - 499
Nhttps://1c.argasmo.ru/ 185.134.232.34
404

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nhttps://185.134.232.34/ 185.134.232.34
404

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain 1c.argasmo.ru, 1 ip addresses, 1 different http results.

2. DNS- and NameServer - Checks

AInfo:: 10 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 10 Queries complete, 10 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.beget.com (5.101.159.11), ns1.beget.pro (5.101.159.11), ns2.beget.com (185.50.27.12), ns2.beget.pro (185.50.27.12)
AGood (1 - 3.0):: An average of 2.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 6 different Name Servers found: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru, 4 Name Servers included in Delegation: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, 6 Name Servers included in 1 Zone definitions: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru, 1 Name Servers listed in SOA.Primary: ns1.beget.com.
AGood: Only one SOA.Primary Name Server found.: ns1.beget.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.beget.com.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns1.beget.com (5.101.159.11): Delegation: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, Zone: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru. Name Servers defined in Zone, missing in Delegation: ns1.beget.ru, ns2.beget.ru.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns1.beget.pro (5.101.159.11): Delegation: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, Zone: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru. Name Servers defined in Zone, missing in Delegation: ns1.beget.ru, ns2.beget.ru.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns1.beget.ru (5.101.159.11): Delegation: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, Zone: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru. Name Servers defined in Zone, missing in Delegation: ns1.beget.ru, ns2.beget.ru.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns2.beget.com (185.50.27.12): Delegation: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, Zone: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru. Name Servers defined in Zone, missing in Delegation: ns1.beget.ru, ns2.beget.ru.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns2.beget.pro (185.50.27.12): Delegation: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, Zone: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru. Name Servers defined in Zone, missing in Delegation: ns1.beget.ru, ns2.beget.ru.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns2.beget.ru (185.50.27.12): Delegation: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, Zone: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru. Name Servers defined in Zone, missing in Delegation: ns1.beget.ru, ns2.beget.ru.
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 6 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 6 different Name Servers found
AGood: Name servers with different Top Level Domains / Public Suffix List entries found: 6 Name Servers, 3 Top Level Domains: ru, pro, com
AGood: Name Servers with different domain names found.: 3 different Domains found
Warning: All Name Servers from the same Country / IP location.: 6 Name Servers, 1 Countries: RU
AInfo: Ipv4-Subnet-list: 6 Name Servers, 2 different subnets (first Byte): 185., 5., 2 different subnets (first two Bytes): 185.50., 5.101., 2 different subnets (first three Bytes): 185.50.27., 5.101.159.
AGood: Name Server IPv4-addresses from different subnet found:
AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.beget.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

3. Content- and Performance-critical Checks

http://1c.argasmo.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.134.232.34
-14

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


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
1c.argasmo.ru
185.134.232.34
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
384
Aes256
256
Sha384
error checking OCSP stapling
ok
1c.argasmo.ru
185.134.232.34
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
384
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN
Tls.1.2
Tls.1.1
Tls.1.0


185.134.232.34
185.134.232.34
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
384
Aes256
256
Sha384
error checking OCSP stapling
ok

185.134.232.34
185.134.232.34
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
384
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Cert sent without SNI
Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN
Cert sent without SNI
Tls.1.2
Tls.1.1
Tls.1.0


9. Certificates

1.
1.
CN=1CDataServer
14.09.2021
14.09.2022
expires in 352 days
1CDataServer - 1 entry
1.
1.
CN=1CDataServer
14.09.2021

14.09.2022
expires in 352 days
1CDataServer - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:458FDA38501902B64945A054F0011E43
Thumbprint:2AC3261DB0275DBB270707469E4BE43E8CD0F689
SHA256 / Certificate:pfS2uH+3+1s/ZP3q0wPWutLDx+csTDDIMg6X0wKKX/E=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):05408097194bb725cb1220a565e33ed1fa0c1fbebc97150455cacf92a9db3af0
SHA256 hex / Subject Public Key Information (SPKI):05408097194bb725cb1220a565e33ed1fa0c1fbebc97150455cacf92a9db3af0 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1)

UntrustedRoot: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.


10. Last Certificates - Certificate Transparency Log Check

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

No CertSpotter - CT-Log entries found


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

No CRT - CT-Log entries found


11. Html-Content - Entries

Summary

Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
https://1c.argasmo.ru/
185.134.232.34
meta
other
1

0


0
0
0

https://185.134.232.34/
185.134.232.34
meta
other
1

0


0
0
0

Details

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsgStatus
https://1c.argasmo.ru/
185.134.232.34
meta
Content-Type
text/html; charset=us-ascii


1
ok







https://185.134.232.34/
185.134.232.34
meta
Content-Type
text/html; charset=us-ascii


1
ok








12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru

QNr.DomainTypeNS used
1
com
NS
h.root-servers.net (2001:500:1::53)

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

Answer: ns2.beget.com
185.50.27.12
3
pro
NS
a.root-servers.net (2001:503:ba3e::2:30)

Answer: a0.pro.afilias-nst.info, a2.pro.afilias-nst.info, b0.pro.afilias-nst.org, b2.pro.afilias-nst.org, c0.pro.afilias-nst.info, d0.pro.afilias-nst.org
4
ns1.beget.pro: 5.101.159.11
NS
a0.pro.afilias-nst.info (2001:500:c0::1)

Answer: ns2.beget.pro
185.50.27.12
5
ru
NS
l.root-servers.net (2001:500:9f::42)

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

Answer: ns1.beget.RU, ns2.beget.RU

Answer: ns1.BEGET.RU
5.101.159.11

Answer: ns2.BEGET.RU
185.50.27.12
7
ns2.beget.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.beget.RU, ns2.beget.RU

Answer: ns1.BEGET.RU
5.101.159.11

Answer: ns2.BEGET.RU
185.50.27.12
8
RU
NS
d.root-servers.net (2001:500:2d::d)

Answer: a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net, f.dns.ripn.net
9
ns1.beget.RU
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.beget.RU, ns2.beget.RU

Answer: ns1.BEGET.RU
5.101.159.11

Answer: ns2.BEGET.RU
185.50.27.12
10
ns2.beget.RU
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.beget.RU, ns2.beget.RU

Answer: ns1.BEGET.RU
5.101.159.11

Answer: ns2.BEGET.RU
185.50.27.12


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
1c.argasmo.ru
0

no CAA entry found
1
0
argasmo.ru
0

no CAA entry found
1
0
ru
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
argasmo.ru
v=spf1 redirect=beget.com
ok
1
0
1c.argasmo.ru

ok
1
0
_acme-challenge.1c.argasmo.ru

Name Error - The domain name does not exist
1
0
_acme-challenge.1c.argasmo.ru.argasmo.ru

Name Error - The domain name does not exist
1
0
_acme-challenge.1c.argasmo.ru.1c.argasmo.ru

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=7a5c416a-aad5-4663-ad97-a00a94a86981


Last Result: https://check-your-website.server-daten.de/?q=1c.argasmo.ru - 2021-09-14 22:54:38


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

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