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


 

 

U

 

No dns entry found - perhaps mistype. Or wrong IDN

 

Checked:
04.02.2025 15:35:44

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
pstpn.ru
CNAME
cdncf.site
yes
1
0
www.pstpn.ru
CNAME
cdncf.site
yes
1
0
*.pstpn.ru
A

yes



AAAA

yes



CNAME
cdncf.site
yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






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






Status: Valid because published






3 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 26470, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.02.2025, 00:00:00 +, Signature-Inception: 31.01.2025, 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 18374, DigestType 2 and Digest gFjQwIjZs/fzAIDiuMmASUQwFyKizOnuZvasdP6y4gA=






1 RRSIG RR to validate DS RR found






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






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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 55728, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 345600 sec, Signature-expiration: 18.02.2025, 00:00:00 +, Signature-Inception: 29.01.2025, 00:00:00 +, KeyTag 18374, Signer-Name: ru






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






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



Zone: pstpn.ru

pstpn.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 "ub7qbusaio6sjl1p3jbcgbh4g14reook" between the hashed NSEC3-owner "ub1psj7bgpeftraqglr6056vde425hkg" and the hashed NextOwner "ub857dl9656uk88fjmti07uj6q4mho78". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner ub1psj7bgpeftraqglr6056vde425hkg.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 26.02.2025, 14:50:53 +, Signature-Inception: 26.01.2025, 14:15:32 +, KeyTag 55728, Signer-Name: ru






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "j20c0qkdhua3cumnkst289ff06u2sq91" as Owner. That's the Hash of "ru" with the NextHashedOwnerName "j21lulr2unpa28sere28ovnjnj67qp7v". So that domain name is the Closest Encloser of "pstpn.ru". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner j20c0qkdhua3cumnkst289ff06u2sq91.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 10.03.2025, 06:10:26 +, Signature-Inception: 24.01.2025, 16:15:29 +, KeyTag 55728, Signer-Name: ru






0 DNSKEY RR found









Zone: www.pstpn.ru

www.pstpn.ru
0 DS RR in the parent zone found



Zone: (root)

(root)
1 DS RR published






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






Status: Valid because published






3 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 26470, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.02.2025, 00:00:00 +, Signature-Inception: 31.01.2025, 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: site

site
2 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 51676, DigestType 2 and Digest iDF19vXGjqgVY7YtGyt5tqmX1g3G4gzHCv0M1rfoL2I=






DS with Algorithm 8, KeyTag 51974, DigestType 2 and Digest oG3EdFfMEYXPGzp89uzLhJeN6Sk53Rgr7tlSFQnQ2ns=






1 RRSIG RR to validate DS RR found






RRSIG-Owner site., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 17.02.2025, 05:00:00 +, Signature-Inception: 04.02.2025, 04:00:00 +, KeyTag 26470, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 24654, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner site., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 28.02.2025, 07:22:37 +, Signature-Inception: 29.01.2025, 05:52:37 +, KeyTag 51974, Signer-Name: site






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






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



Zone: cdncf.site

cdncf.site
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 "id6i9iuja1r8ho1n7h5lmle6e4hmjbu8" between the hashed NSEC3-owner "id4d0kvhrlr1hbe73ehs9o5rb1l5p7d6" and the hashed NextOwner "id6mon2ph6o2jp0jjb4kimdl85vh5maa". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner id4d0kvhrlr1hbe73ehs9o5rb1l5p7d6.site., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 13.02.2025, 20:47:02 +, Signature-Inception: 14.01.2025, 19:17:02 +, KeyTag 24654, Signer-Name: site






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "kkkldpnn5k2662ei72hm1tvtee3uakea" as Owner. That's the Hash of "site" with the NextHashedOwnerName "kkletpllcs8l9v4016d5lhccgrim8hq6". So that domain name is the Closest Encloser of "cdncf.site". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner kkkldpnn5k2662ei72hm1tvtee3uakea.site., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 28.02.2025, 07:22:37 +, Signature-Inception: 29.01.2025, 05:52:37 +, KeyTag 24654, Signer-Name: site






0 DNSKEY RR found







 

3. Name Servers

DomainNameserverNS-IP
pstpn.ru
  ns1.platformcraft.ru / a4f6cf0d63ae
5.188.121.99
Moscow/Russia (RU) - EdgeCenter LLC


  ns2.platformcraft.com / a4f6cf0d63ae
5.188.121.99
Moscow/Russia (RU) - EdgeCenter LLC

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


  b.dns.ripn.net / tau-std.ripn.net


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


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


  f.dns.ripn.net / gamma-vlv.ripn.net


cdncf.site
  ns1.platformcraft.ru / 546ab28cfe54
5.188.121.99
Moscow/Russia (RU) - EdgeCenter LLC


  ns2.platformcraft.com / 546ab28cfe54
5.188.121.99
Moscow/Russia (RU) - EdgeCenter LLC

site
  a.nic.site / PGXL-PS5KRW-2C7ZTP


  b.nic.site / PDUS-VJ5JVS-CTI2KM


  e.nic.site / SFQY-BG7AF9-XTW0MS


  f.nic.site / PDUS-VJ5JVS-CTI2KM


  ns0.centralnic.net

 

4. SOA-Entries


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


Domain:pstpn.ru
Zone-Name:pstpn.ru
Primary:ns1.platformcraft.ru
Mail:care@platformcraft.ru
Serial:1738679608
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:2



Domain:site
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:site
Zone-Name:site
Primary:ns0.centralnic.net
Mail:hostmaster.centralnic.net
Serial:394615
Refresh:900
Retry:1800
Expire:6048000
TTL:3600
num Entries:4


Domain:cdncf.site
Zone-Name:cdncf.site
Primary:ns1.platformcraft.ru
Mail:care@platformcraft.ru
Serial:1738679539
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:2


5. Screenshots

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

 

 

6. Url-Checks

DomainnameHttp-StatusredirectSec.G








 

7. Comments


1. General Results, most used to calculate the result

Aname "pstpn.ru" is domain, 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: 3093 (complete: 263653)
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.pstpn.ru

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 54 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 54 Queries complete, 53 with IPv6, 1 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
Bad (greater 8):: An average of 27.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns1.platformcraft.ru, ns2.platformcraft.com, 2 Name Servers included in Delegation: ns1.platformcraft.ru, ns2.platformcraft.com, 2 Name Servers included in 1 Zone definitions: ns1.platformcraft.ru, ns2.platformcraft.com, 1 Name Servers listed in SOA.Primary: ns1.platformcraft.ru.
AGood: Only one SOA.Primary Name Server found.: ns1.platformcraft.ru.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.platformcraft.ru.
AGood: Consistency 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. Ordered list of name servers: ns1.platformcraft.ru, ns2.platformcraft.com
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: 2 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 different Name Servers found
AGood: Name servers with different Top Level Domains / Public Suffix List entries found: 2 Name Servers, 2 Top Level Domains: ru, com
AGood: Name Servers with different domain names found.: 2 different Domains found
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: RU
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 5., 1 different subnets (first two Bytes): 5.188., 1 different subnets (first three Bytes): 5.188.121.
XFatal: All Name Server IPv4 addresses from the same subnet. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.:
XFatal: Only one Name Server IPv4 address found. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: a.nic.site: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (PGXL-PS5KRW-2C7ZTP). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: e.nic.site: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (SFQY-BG7AF9-XTW0MS). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns0.centralnic.net: 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.
Nameserver doesn't pass all EDNS-Checks: ns1.platformcraft.ru / 5.188.121.99: OP100: ok. FLAGS: ok. V1: ok. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok (546ab28cfe54). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.platformcraft.ru / 5.188.121.99: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (a4f6cf0d63ae). COOKIE: ok. CLIENTSUBNET: fatal timeout.
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.

4. Content- and Performance-critical Checks

Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (not Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 63646 milliseconds, 63.646 seconds

 

8. Connections

No connection informations found. Perhaps only http - connections.

 

9. Certificates

No certificate informations found. Perhaps only http - connections.

 

10. Last Certificates - Certificate Transparency Log Check

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

Issuerlast 7 daysactivenum Certs
CN=R10, O=Let's Encrypt, C=US
0
4
4
CN=R11, O=Let's Encrypt, C=US
0
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
9343242502
leaf cert
CN=R10, O=Let's Encrypt, C=US
2025-01-28 08:34:45
2025-04-28 08:34:44
pstpn.ru - 1 entries


9343231375
leaf cert
CN=R11, O=Let's Encrypt, C=US
2025-01-28 08:32:28
2025-04-28 08:32:27
pstpn.ru - 1 entries


9343230600
leaf cert
CN=R10, O=Let's Encrypt, C=US
2025-01-28 08:31:57
2025-04-28 08:31:56
pstpn.ru - 1 entries


9343213884
leaf cert
CN=R10, O=Let's Encrypt, C=US
2025-01-28 08:31:20
2025-04-28 08:31:19
pstpn.ru - 1 entries


9343007895
leaf cert
CN=R10, O=Let's Encrypt, C=US
2025-01-28 08:02:24
2025-04-28 08:02:23
pstpn.ru - 1 entries


 

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

No CRT - CT-Log entries found

 

11. Html-Content - Entries

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

 

12. Html-Parsing via https://validator.w3.org/nu/


No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

 

13. Nameserver - IP-Adresses

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

 

QNr.DomainTypeNS used
1
ru
NS
d.root-servers.net (199.7.91.13)

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

Answer: ns-1534.awsdns-63.org, ns-1857.awsdns-40.co.uk, ns-220.awsdns-27.com, ns-523.awsdns-01.net, ns4-cloud.nic.RU, ns4-l2.nic.RU, ns8-cloud.nic.RU, ns8-l2.nic.RU

Answer: ns8-cloud.nic.RU
194.67.73.80, 194.67.73.82, 89.104.93.31, 89.104.93.35, 89.104.93.36, 89.104.95.31, 89.104.95.35, 89.104.95.36
3
com
NS
f.root-servers.net (2001:500:2f::f)

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

Answer: ns-1449.awsdns-53.org, ns-1549.awsdns-01.co.uk, ns-198.awsdns-24.com, ns-965.awsdns-56.net, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru

Answer: ns-198.awsdns-24.com
205.251.192.198
5
org
NS
b.root-servers.net (2001:500:200::b)

Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
6
ns-1534.awsdns-63.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: g-ns-1283.awsdns-63.org, g-ns-1663.awsdns-63.org, g-ns-191.awsdns-63.org, g-ns-962.awsdns-63.org

Answer: g-ns-1283.awsdns-63.org
205.251.197.3, 2600:9000:5305:300::1

Answer: g-ns-1663.awsdns-63.org
205.251.198.127, 2600:9000:5306:7f00::1

Answer: g-ns-191.awsdns-63.org
205.251.192.191, 2600:9000:5300:bf00::1

Answer: g-ns-962.awsdns-63.org
205.251.195.194, 2600:9000:5303:c200::1
7
uk
NS
k.root-servers.net (2001:7fd::1)

Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
8
ns-1857.awsdns-40.co.uk
NS
dns1.nic.uk (2a01:618:400::1)

Answer: g-ns-1515.awsdns-40.co.uk, g-ns-1836.awsdns-40.co.uk, g-ns-360.awsdns-40.co.uk, g-ns-936.awsdns-40.co.uk

Answer: g-ns-1515.awsdns-40.co.uk
205.251.197.235, 2600:9000:5305:eb00::1

Answer: g-ns-1836.awsdns-40.co.uk
205.251.199.44, 2600:9000:5307:2c00::1

Answer: g-ns-360.awsdns-40.co.uk
205.251.193.104, 2600:9000:5301:6800::1

Answer: g-ns-936.awsdns-40.co.uk
205.251.195.168, 2600:9000:5303:a800::1
9
ns-220.awsdns-27.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: g-ns-1179.awsdns-27.com, g-ns-1755.awsdns-27.com, g-ns-28.awsdns-27.com, g-ns-603.awsdns-27.com

Answer: g-ns-1179.awsdns-27.com
205.251.196.155, 2600:9000:5304:9b00::1

Answer: g-ns-1755.awsdns-27.com
205.251.198.219, 2600:9000:5306:db00::1

Answer: g-ns-28.awsdns-27.com
205.251.192.28, 2600:9000:5300:1c00::1

Answer: g-ns-603.awsdns-27.com
205.251.194.91, 2600:9000:5302:5b00::1
10
net
NS
d.root-servers.net (2001:500:2d::d)

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
11
ns-523.awsdns-01.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: g-ns-1345.awsdns-01.net, g-ns-1921.awsdns-01.net, g-ns-450.awsdns-01.net, g-ns-771.awsdns-01.net

Answer: g-ns-1345.awsdns-01.net
205.251.197.65, 2600:9000:5305:4100::1

Answer: g-ns-1921.awsdns-01.net
205.251.199.129, 2600:9000:5307:8100::1

Answer: g-ns-450.awsdns-01.net
205.251.193.194, 2600:9000:5301:c200::1

Answer: g-ns-771.awsdns-01.net
205.251.195.3, 2600:9000:5303:300::1
12
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
13
ns4-cloud.nic.RU
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU

Answer: ns5.nic.RU
2a02:2090:e800:9000:31:177:67:100, 31.177.67.100

Answer: ns6.nic.RU
2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100

Answer: ns9.nic.RU
2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
14
ns4-l2.nic.RU
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU

Answer: ns5.nic.RU
2a02:2090:e800:9000:31:177:67:100, 31.177.67.100

Answer: ns6.nic.RU
2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100

Answer: ns9.nic.RU
2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
15
ns8-l2.nic.RU
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU

Answer: ns5.nic.RU
2a02:2090:e800:9000:31:177:67:100, 31.177.67.100

Answer: ns6.nic.RU
2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100

Answer: ns9.nic.RU
2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
16
ns-1449.awsdns-53.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: g-ns-1080.awsdns-53.org, g-ns-1653.awsdns-53.org, g-ns-181.awsdns-53.org, g-ns-759.awsdns-53.org

Answer: g-ns-1080.awsdns-53.org
205.251.196.56, 2600:9000:5304:3800::1

Answer: g-ns-1653.awsdns-53.org
205.251.198.117, 2600:9000:5306:7500::1

Answer: g-ns-181.awsdns-53.org
205.251.192.181, 2600:9000:5300:b500::1

Answer: g-ns-759.awsdns-53.org
205.251.194.247, 2600:9000:5302:f700::1
17
ns-1549.awsdns-01.co.uk
NS
dns1.nic.uk (2a01:618:400::1)

Answer: g-ns-1476.awsdns-01.co.uk, g-ns-1797.awsdns-01.co.uk, g-ns-321.awsdns-01.co.uk, g-ns-897.awsdns-01.co.uk

Answer: g-ns-1476.awsdns-01.co.uk
205.251.197.196, 2600:9000:5305:c400::1

Answer: g-ns-1797.awsdns-01.co.uk
205.251.199.5, 2600:9000:5307:500::1

Answer: g-ns-321.awsdns-01.co.uk
205.251.193.65, 2600:9000:5301:4100::1

Answer: g-ns-897.awsdns-01.co.uk
205.251.195.129, 2600:9000:5303:8100::1
18
ns-965.awsdns-56.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: g-ns-1400.awsdns-56.net, g-ns-1976.awsdns-56.net, g-ns-505.awsdns-56.net, g-ns-826.awsdns-56.net

Answer: g-ns-1400.awsdns-56.net
205.251.197.120, 2600:9000:5305:7800::1

Answer: g-ns-1976.awsdns-56.net
205.251.199.184, 2600:9000:5307:b800::1

Answer: g-ns-505.awsdns-56.net
205.251.193.249, 2600:9000:5301:f900::1

Answer: g-ns-826.awsdns-56.net
205.251.195.58, 2600:9000:5303:3a00::1
19
ns4-cloud.nic.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU

Answer: ns5.nic.RU
2a02:2090:e800:9000:31:177:67:100, 31.177.67.100

Answer: ns6.nic.RU
2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100

Answer: ns9.nic.RU
2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
20
ns4-l2.nic.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU

Answer: ns5.nic.RU
2a02:2090:e800:9000:31:177:67:100, 31.177.67.100

Answer: ns6.nic.RU
2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100

Answer: ns9.nic.RU
2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
21
ns8-cloud.nic.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU

Answer: ns5.nic.RU
2a02:2090:e800:9000:31:177:67:100, 31.177.67.100

Answer: ns6.nic.RU
2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100

Answer: ns9.nic.RU
2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
22
ns8-l2.nic.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU

Answer: ns5.nic.RU
2a02:2090:e800:9000:31:177:67:100, 31.177.67.100

Answer: ns6.nic.RU
2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100

Answer: ns9.nic.RU
2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
23
ns-1534.awsdns-63.org: 205.251.197.254
A
g-ns-1283.awsdns-63.org (2600:9000:5305:300::1)
24
ns-1534.awsdns-63.org: 2600:9000:5305:fe00::1
AAAA
g-ns-1283.awsdns-63.org (2600:9000:5305:300::1)
25
ns-1857.awsdns-40.co.uk: 205.251.199.65
A
g-ns-1515.awsdns-40.co.uk (2600:9000:5305:eb00::1)
26
ns-1857.awsdns-40.co.uk: 2600:9000:5307:4100::1
AAAA
g-ns-1515.awsdns-40.co.uk (2600:9000:5305:eb00::1)
27
ns-220.awsdns-27.com: 205.251.192.220
A
g-ns-1179.awsdns-27.com (2600:9000:5304:9b00::1)
28
ns-220.awsdns-27.com: 2600:9000:5300:dc00::1
AAAA
g-ns-1179.awsdns-27.com (2600:9000:5304:9b00::1)
29
ns-523.awsdns-01.net: 205.251.194.11
A
g-ns-1345.awsdns-01.net (2600:9000:5305:4100::1)
30
ns-523.awsdns-01.net: 2600:9000:5302:b00::1
AAAA
g-ns-1345.awsdns-01.net (2600:9000:5305:4100::1)
31
ns4-cloud.nic.RU: 89.104.93.30, 89.104.93.33, 89.104.93.34, 89.104.95.30, 89.104.95.33, 89.104.95.34
A
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
32
ns4-cloud.nic.RU: No AAAA record found
AAAA
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
33
ns4-l2.nic.RU: 91.217.20.20
A
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
34
ns4-l2.nic.RU: No AAAA record found
AAAA
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
35
ns8-l2.nic.RU: 91.217.21.20
A
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
36
ns8-l2.nic.RU: No AAAA record found
AAAA
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
37
ns-1449.awsdns-53.org: 205.251.197.169
A
g-ns-1080.awsdns-53.org (2600:9000:5304:3800::1)
38
ns-1449.awsdns-53.org: 2600:9000:5305:a900::1
AAAA
g-ns-1080.awsdns-53.org (2600:9000:5304:3800::1)
39
ns-1549.awsdns-01.co.uk: 205.251.198.13
A
g-ns-1476.awsdns-01.co.uk (2600:9000:5305:c400::1)
40
ns-1549.awsdns-01.co.uk: 2600:9000:5306:d00::1
AAAA
g-ns-1476.awsdns-01.co.uk (2600:9000:5305:c400::1)
41
ns-965.awsdns-56.net: 205.251.195.197
A
g-ns-1400.awsdns-56.net (2600:9000:5305:7800::1)
42
ns-965.awsdns-56.net: 2600:9000:5303:c500::1
AAAA
g-ns-1400.awsdns-56.net (2600:9000:5305:7800::1)
43
ns4-cloud.nic.ru: 89.104.93.30, 89.104.93.33, 89.104.93.34, 89.104.95.30, 89.104.95.33, 89.104.95.34
A
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
44
ns4-cloud.nic.ru: No AAAA record found
AAAA
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
45
ns4-l2.nic.ru: 91.217.20.20
A
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
46
ns4-l2.nic.ru: No AAAA record found
AAAA
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
47
ns8-cloud.nic.ru: 89.104.93.31, 89.104.93.35, 89.104.93.36, 89.104.95.31, 89.104.95.35, 89.104.95.36
A
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
48
ns8-cloud.nic.ru: No AAAA record found
AAAA
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
49
ns8-l2.nic.ru: 91.217.21.20
A
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
50
ns8-l2.nic.ru: No AAAA record found
AAAA
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
51
ns1.platformcraft.ru: 5.188.121.99
A
ns-1534.awsdns-63.org (2600:9000:5305:fe00::1)
52
ns1.platformcraft.ru: No AAAA record found
AAAA
ns-1534.awsdns-63.org (2600:9000:5305:fe00::1)
53
ns2.platformcraft.com: 5.188.121.99
A
ns-1449.awsdns-53.org (2600:9000:5305:a900::1)
54
ns2.platformcraft.com: No AAAA record found
AAAA
ns-1449.awsdns-53.org (2600:9000:5305:a900::1)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.pstpn.ru



1
0
cdncf.site
0

no CAA entry found
1
0
pstpn.ru



1
0
site
0

no CAA entry found
1
0
ru
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
pstpn.ru


1
0
cdncf.site

ok
1
0
www.pstpn.ru
98FqwfnWL3DwIlmu9x91aEfXY2p3cQkbeSclrW624fA
looks good, but no _acme-challenge in domain name?
1
0
_acme-challenge.pstpn.ru
98FqwfnWL3DwIlmu9x91aEfXY2p3cQkbeSclrW624fA
looks good, correct length, correct characters
1
0
_acme-challenge.cdncf.site
_akAFT_-lE9MSOiBZEqUtBT-ly1stE-yDk8RRj1CWHs
looks good, correct length, correct characters
1
0
_acme-challenge.cdncf.site
AIwK51fmG0AFM6JdrWe0_g0R4r_ymHYiC_liISmvK_U
looks good, correct length, correct characters
1
0
_acme-challenge.cdncf.site
ElXXQ7E8abCm-isj0Wc9XC1HsyvOtN8bd3GakZZjc58
looks good, correct length, correct characters
1
0
_acme-challenge.cdncf.site
Ez0y6slZprEqTx8X9uZR2AKIt3PLhuCke4nWVckuAfo
looks good, correct length, correct characters
1
0
_acme-challenge.www.pstpn.ru
98FqwfnWL3DwIlmu9x91aEfXY2p3cQkbeSclrW624fA
looks good, correct length, correct characters
1
0
_acme-challenge.pstpn.ru.pstpn.ru
98FqwfnWL3DwIlmu9x91aEfXY2p3cQkbeSclrW624fA
perhaps wrong
1
0
_acme-challenge.cdncf.site.cdncf.site
_akAFT_-lE9MSOiBZEqUtBT-ly1stE-yDk8RRj1CWHs
perhaps wrong
1
0
_acme-challenge.www.pstpn.ru.pstpn.ru
98FqwfnWL3DwIlmu9x91aEfXY2p3cQkbeSclrW624fA
perhaps wrong
1
0
_acme-challenge.cdncf.site.cdncf.site
AIwK51fmG0AFM6JdrWe0_g0R4r_ymHYiC_liISmvK_U
perhaps wrong
1
0
_acme-challenge.cdncf.site.cdncf.site
ElXXQ7E8abCm-isj0Wc9XC1HsyvOtN8bd3GakZZjc58
perhaps wrong
1
0
_acme-challenge.cdncf.site.cdncf.site
Ez0y6slZprEqTx8X9uZR2AKIt3PLhuCke4nWVckuAfo
perhaps wrong
1
0
_acme-challenge.www.pstpn.ru.www.pstpn.ru
98FqwfnWL3DwIlmu9x91aEfXY2p3cQkbeSclrW624fA
perhaps wrong
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
_mta-sts
CNAME
_mta-sts.pstpn.ru

cdncf.site
ok
SPF
TXT
pstpn.ru

32768TXT expected, but CNAME found. CNAME not allowed, only TXT queries are allowed. See RFC 7208, 4.4.

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

 

 

Permalink: https://check-your-website.server-daten.de/?i=6166acd4-1bc5-45e2-b994-ee2d49074f49

 

Last Result: https://check-your-website.server-daten.de/?q=pstpn.ru - 2025-02-04 15:35:44

 

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

 

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

 

 

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=pstpn.ru