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

0 in Queue, 1 of max. 8 Checks (23:36:58)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

X

 

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

 

Checked:
10.01.2025 16:54:33

 

Older results

 

U - 10.01.2025 16:02:57
U - 10.01.2025 14:33:36

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
newbot.sevasvpn.ru
A
185.233.200.191
Moscow/Russia (RU) - First Server Limited
Hostname: sevasvpn.ru
yes
2
1

AAAA

yes


www.newbot.sevasvpn.ru

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



AAAA
Name Error
yes



CNAME
Name Error
yes



CNAME
Name Error
yes


*.newbot.sevasvpn.ru
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






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






• Status: Valid because published






3 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 26470, Flags 256






Public Key with Algorithm 8, KeyTag 61050, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.01.2025, 00:00:00 +, Signature-Inception: 01.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: 23.01.2025, 05:00:00 +, Signature-Inception: 10.01.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: 29.01.2025, 00:00:00 +, Signature-Inception: 09.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: sevasvpn.ru

sevasvpn.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 "btuvu5eticchnhu0lkd3fi41atmf38sh" between the hashed NSEC3-owner "btut6k8g0ug0jlgi4eoter0a2f52bs05" and the hashed NextOwner "bu26mkrdga64ppf1ddv23nl95e0sdb96". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner btut6k8g0ug0jlgi4eoter0a2f52bs05.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.01.2025, 05:44:15 +, Signature-Inception: 24.12.2024, 14:14:51 +, 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 "sevasvpn.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: 30.01.2025, 16:17:45 +, Signature-Inception: 24.12.2024, 14:14:51 +, KeyTag 55728, Signer-Name: ru






0 DNSKEY RR found









Zone: newbot.sevasvpn.ru

newbot.sevasvpn.ru
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: www.newbot.sevasvpn.ru

www.newbot.sevasvpn.ru
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.newbot.sevasvpn.ru
•  firstbytedns.net

newbot.sevasvpn.ru
X  firstbytedns.net

sevasvpn.ru
•  firstbytedns.net


T  ns1.firstbytedns.net
185.104.248.26
Moscow/Russia (RU) - First Server Limited		•

X 
2a04:5200:ffff::320b
Moscow/Russia (RU) - NTX Technologies s.r.o.

•  ns1.firstbytedns.ru
185.104.248.26
Moscow/Russia (RU) - First Server Limited		•

• 
2a04:5200:ffff::320b
Moscow/Russia (RU) - NTX Technologies s.r.o.		•

T  ns2.firstbytedns.net
185.104.248.27
Moscow/Russia (RU) - First Server Limited

T 
2a04:5200:ffff::35de
Moscow/Russia (RU) - NTX Technologies s.r.o.		•

•  ns2.firstbytedns.ru
185.104.248.27
Moscow/Russia (RU) - First Server Limited		•

• 
2a04:5200:ffff::35de
Moscow/Russia (RU) - NTX Technologies s.r.o.		•

•  ns3.firstbytedns.net
185.180.230.222
Moscow/Russia (RU) - NTX Technologies s.r.o.		•

• 
2a04:5200:ffff::115d
Moscow/Russia (RU) - NTX Technologies s.r.o.		•

•  ns3.firstbytedns.ru
185.180.230.222
Moscow/Russia (RU) - NTX Technologies s.r.o.		•

• 
2a04:5200:ffff::115d
Moscow/Russia (RU) - NTX Technologies s.r.o.		•
ru
•  a.dns.ripn.net / tau.ripn.net
•

T  b.dns.ripn.net / std-tau-02.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
•

 

4. SOA-Entries


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


Domain:sevasvpn.ru
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:2


Domain:sevasvpn.ru
Zone-Name:sevasvpn.ru
Primary:firstbytedns.net
Mail:w0w4lolnn.mail.ru
Serial:2025011001
Refresh:3600
Retry:3600
Expire:604800
TTL:86400
num Entries:11


Domain:newbot.sevasvpn.ru
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


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


5. Screenshots

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

 

 

6. Url-Checks

DomainnameHttp-StatusredirectSec.G
• http://newbot.sevasvpn.ru/
185.233.200.191
-102


1.200
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (185.233.200.191:80)

• https://newbot.sevasvpn.ru/
185.233.200.191
-102


1.204
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (185.233.200.191:443)

• http://newbot.sevasvpn.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
185.233.200.191
-102


1.206
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (185.233.200.191:80)
Visible Content:

• https://185.233.200.191/
185.233.200.191
-102


1.194
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (185.233.200.191:443)

 

7. Comments


1. General Results, most used to calculate the result

Aname "newbot.sevasvpn.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: 3093 (complete: 263653)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: newbot.sevasvpn.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: newbot.sevasvpn.ru has no ipv6 address.
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.
Vhttp://newbot.sevasvpn.ru/ 185.233.200.191
-102

Connect failure - perhaps firewall
Vhttps://newbot.sevasvpn.ru/ 185.233.200.191
-102

Connect failure - perhaps firewall
Vhttp://newbot.sevasvpn.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.233.200.191
-102

Connect failure - perhaps firewall
Vhttps://185.233.200.191/ 185.233.200.191
-102

Connect failure - perhaps firewall
XFatal error: Nameserver doesn't support TCP connection: firstbytedns.net: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns1.firstbytedns.net / 2a04:5200:ffff::320b: Fatal error (-14). Details: Unable to read data from the transport connection: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.. - Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat
XFatal error: Nameserver doesn't support TCP connection: ns2.firstbytedns.net / 185.104.248.27: Timeout
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain newbot.sevasvpn.ru, 1 ip addresses.
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.newbot.sevasvpn.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:: 12 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 6 Name Servers.
AInfo:: 12 Queries complete, 6 with IPv6, 4 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.
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.firstbytedns.net (185.104.248.26), ns2.firstbytedns.net (185.104.248.27), ns3.firstbytedns.net (185.180.230.222)
AGood (1 - 3.0):: An average of 2.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 7 different Name Servers found: firstbytedns.net, ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru, 2 Name Servers included in Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, 6 Name Servers included in 2 Zone definitions: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru, 1 Name Servers listed in SOA.Primary: firstbytedns.net.
AGood: Only one SOA.Primary Name Server found.: firstbytedns.net.
Error: SOA.Primary Name Server not included in the delegation set.: firstbytedns.net.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.firstbytedns.net (185.104.248.26): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.firstbytedns.net (2a04:5200:ffff::320b): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.firstbytedns.ru (185.104.248.26): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.firstbytedns.ru (2a04:5200:ffff::320b): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.firstbytedns.net (185.104.248.27): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.firstbytedns.net (2a04:5200:ffff::35de): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.firstbytedns.ru (185.104.248.27): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.firstbytedns.ru (2a04:5200:ffff::35de): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.firstbytedns.net (185.180.230.222): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.firstbytedns.net (2a04:5200:ffff::115d): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.firstbytedns.ru (185.180.230.222): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.firstbytedns.ru (2a04:5200:ffff::115d): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru.
AGood: All Name Server Domain Names have a Public Suffix.
Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1

AInfo: Ipv4-Subnet-list: 6 Name Servers, 1 different subnets (first Byte): 185., 2 different subnets (first two Bytes): 185.104., 185.180., 2 different subnets (first three Bytes): 185.104.248., 185.180.230.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 6 Name Servers with IPv6, 1 different subnets (first block): 2a04:, 1 different subnets (first two blocks): 2a04:5200:, 1 different subnets (first three blocks): 2a04:5200:ffff:, 1 different subnets (first four blocks): 2a04:5200:ffff:0000:
Fatal: All Name Server IPv6 addresses from the same subnet.
XNameserver Timeout checking Echo Capitalization: b.dns.ripn.net
XNameserver Timeout checking Echo Capitalization: ns1.firstbytedns.net / 185.104.248.26
XNameserver Timeout checking Echo Capitalization: ns2.firstbytedns.net / 185.104.248.27
XNameserver Timeout checking Echo Capitalization: ns2.firstbytedns.net / 2a04:5200:ffff::35de
Nameserver doesn't pass all EDNS-Checks: b.dns.ripn.net: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (std-tau-02.ripn.net). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: firstbytedns.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: firstbytedns.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: firstbytedns.net: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: ns1.firstbytedns.net / 185.104.248.26: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: ns1.firstbytedns.net / 2a04:5200:ffff::320b: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.firstbytedns.ru / 185.104.248.26: OP100: ok. FLAGS: ok. V1: ok. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.firstbytedns.ru / 2a04:5200:ffff::320b: OP100: fatal timeout. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.firstbytedns.net / 2a04:5200:ffff::35de: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.firstbytedns.ru / 185.104.248.27: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.firstbytedns.ru / 2a04:5200:ffff::35de: OP100: ok. FLAGS: ok. V1: ok. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: ns3.firstbytedns.net / 2a04:5200:ffff::115d: OP100: ok. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.firstbytedns.ru / 2a04:5200:ffff::115d: OP100: ok. FLAGS: ok. V1: ok. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
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

http://newbot.sevasvpn.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.233.200.191
-102

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

 

8. Connections

No connection informations found. Perhaps only http - connections.

 

9. Certificates

No certificate informations found. Perhaps only http - connections.

 

10. Last Certificates - Certificate Transparency Log Check

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

No CertSpotter - CT-Log entries found

 

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 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.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru

 

QNr.DomainTypeNS used
1
net
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.firstbytedns.net: 185.104.248.26
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns2.firstbytedns.net
185.104.248.27

Answer: ns3.firstbytedns.net
185.180.230.222
3
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
4
ns1.firstbytedns.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.firstbytedns.RU, ns2.firstbytedns.RU, ns3.firstbytedns.RU

Answer: ns1.firstbytedns.RU
185.104.248.26

Answer: ns2.firstbytedns.RU
185.104.248.27

Answer: ns3.firstbytedns.RU
185.180.230.222
5
ns2.firstbytedns.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.firstbytedns.RU, ns2.firstbytedns.RU, ns3.firstbytedns.RU

Answer: ns1.firstbytedns.RU
185.104.248.26

Answer: ns2.firstbytedns.RU
185.104.248.27

Answer: ns3.firstbytedns.RU
185.180.230.222
6
ns3.firstbytedns.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.firstbytedns.RU, ns2.firstbytedns.RU, ns3.firstbytedns.RU

Answer: ns1.firstbytedns.RU
185.104.248.26

Answer: ns2.firstbytedns.RU
185.104.248.27

Answer: ns3.firstbytedns.RU
185.180.230.222
7
ns1.firstbytedns.ru: 185.104.248.26
A
ns1.firstbytedns.ru (185.104.248.26)
9
ns2.firstbytedns.ru: 185.104.248.27
A
ns1.firstbytedns.ru (185.104.248.26)
11
ns3.firstbytedns.ru: 185.180.230.222
A
ns1.firstbytedns.ru (185.104.248.26)
12
ns3.firstbytedns.ru: 2a04:5200:ffff::115d
AAAA
ns1.firstbytedns.ru (185.104.248.26)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
newbot.sevasvpn.ru
0

no CAA entry found
1
0
sevasvpn.ru
0

no CAA entry found
1
0
ru
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
sevasvpn.ru

ok
1
0
newbot.sevasvpn.ru

ok
1
0
_acme-challenge.newbot.sevasvpn.ru

Name Error - The domain name does not exist
1
0
_acme-challenge.newbot.sevasvpn.ru.sevasvpn.ru

Name Error - The domain name does not exist
1
0
_acme-challenge.newbot.sevasvpn.ru.newbot.sevasvpn.ru

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No results

 

18. Portchecks

DomainIPPortDescriptionResultAnswer
newbot.sevasvpn.ru
185.233.200.191
21
FTP



newbot.sevasvpn.ru
185.233.200.191
21
FTP



newbot.sevasvpn.ru
185.233.200.191
22
SSH
open
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.10

newbot.sevasvpn.ru
185.233.200.191
22
SSH
open
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.10
Bad: SSH without DNS SSHFP Record found
newbot.sevasvpn.ru
185.233.200.191
25
SMTP



newbot.sevasvpn.ru
185.233.200.191
25
SMTP



newbot.sevasvpn.ru
185.233.200.191
53
DNS



newbot.sevasvpn.ru
185.233.200.191
53
DNS



newbot.sevasvpn.ru
185.233.200.191
110
POP3



newbot.sevasvpn.ru
185.233.200.191
110
POP3



newbot.sevasvpn.ru
185.233.200.191
143
IMAP



newbot.sevasvpn.ru
185.233.200.191
143
IMAP



newbot.sevasvpn.ru
185.233.200.191
465
SMTP (encrypted)



newbot.sevasvpn.ru
185.233.200.191
465
SMTP (encrypted)



newbot.sevasvpn.ru
185.233.200.191
587
SMTP (encrypted, submission)



newbot.sevasvpn.ru
185.233.200.191
587
SMTP (encrypted, submission)



newbot.sevasvpn.ru
185.233.200.191
993
IMAP (encrypted)



newbot.sevasvpn.ru
185.233.200.191
993
IMAP (encrypted)



newbot.sevasvpn.ru
185.233.200.191
995
POP3 (encrypted)



newbot.sevasvpn.ru
185.233.200.191
995
POP3 (encrypted)



newbot.sevasvpn.ru
185.233.200.191
1433
MS SQL



newbot.sevasvpn.ru
185.233.200.191
1433
MS SQL



newbot.sevasvpn.ru
185.233.200.191
2082
cPanel (http)



newbot.sevasvpn.ru
185.233.200.191
2082
cPanel (http)



newbot.sevasvpn.ru
185.233.200.191
2083
cPanel (https)



newbot.sevasvpn.ru
185.233.200.191
2083
cPanel (https)



newbot.sevasvpn.ru
185.233.200.191
2086
WHM (http)



newbot.sevasvpn.ru
185.233.200.191
2086
WHM (http)



newbot.sevasvpn.ru
185.233.200.191
2087
WHM (https)



newbot.sevasvpn.ru
185.233.200.191
2087
WHM (https)



newbot.sevasvpn.ru
185.233.200.191
2089
cPanel Licensing



newbot.sevasvpn.ru
185.233.200.191
2089
cPanel Licensing



newbot.sevasvpn.ru
185.233.200.191
2095
cPanel Webmail (http)



newbot.sevasvpn.ru
185.233.200.191
2095
cPanel Webmail (http)



newbot.sevasvpn.ru
185.233.200.191
2096
cPanel Webmail (https)



newbot.sevasvpn.ru
185.233.200.191
2096
cPanel Webmail (https)



newbot.sevasvpn.ru
185.233.200.191
2222
DirectAdmin (http)



newbot.sevasvpn.ru
185.233.200.191
2222
DirectAdmin (http)



newbot.sevasvpn.ru
185.233.200.191
2222
DirectAdmin (https)



newbot.sevasvpn.ru
185.233.200.191
2222
DirectAdmin (https)



newbot.sevasvpn.ru
185.233.200.191
3306
mySql



newbot.sevasvpn.ru
185.233.200.191
3306
mySql



newbot.sevasvpn.ru
185.233.200.191
5224
Plesk Licensing



newbot.sevasvpn.ru
185.233.200.191
5224
Plesk Licensing



newbot.sevasvpn.ru
185.233.200.191
5432
PostgreSQL



newbot.sevasvpn.ru
185.233.200.191
5432
PostgreSQL



newbot.sevasvpn.ru
185.233.200.191
8080
Ookla Speedtest (http)



newbot.sevasvpn.ru
185.233.200.191
8080
Ookla Speedtest (http)



newbot.sevasvpn.ru
185.233.200.191
8080
Ookla Speedtest (https)



newbot.sevasvpn.ru
185.233.200.191
8080
Ookla Speedtest (https)



newbot.sevasvpn.ru
185.233.200.191
8083
VestaCP http



newbot.sevasvpn.ru
185.233.200.191
8083
VestaCP http



newbot.sevasvpn.ru
185.233.200.191
8083
VestaCP https



newbot.sevasvpn.ru
185.233.200.191
8083
VestaCP https



newbot.sevasvpn.ru
185.233.200.191
8443
Plesk Administration (https)



newbot.sevasvpn.ru
185.233.200.191
8443
Plesk Administration (https)



newbot.sevasvpn.ru
185.233.200.191
8447
Plesk Installer + Updates



newbot.sevasvpn.ru
185.233.200.191
8447
Plesk Installer + Updates



newbot.sevasvpn.ru
185.233.200.191
8880
Plesk Administration (http)



newbot.sevasvpn.ru
185.233.200.191
8880
Plesk Administration (http)



newbot.sevasvpn.ru
185.233.200.191
10000
Webmin (http)



newbot.sevasvpn.ru
185.233.200.191
10000
Webmin (http)



newbot.sevasvpn.ru
185.233.200.191
10000
Webmin (https)



newbot.sevasvpn.ru
185.233.200.191
10000
Webmin (https)



 

 

Permalink: https://check-your-website.server-daten.de/?i=a6527eac-e940-4b93-82a9-03c36626da73

 

Last Result: https://check-your-website.server-daten.de/?q=newbot.sevasvpn.ru - 2025-01-10 16:54:33

 

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

 

<a href="https://check-your-website.server-daten.de/?q=newbot.sevasvpn.ru" target="_blank">Check this Site: newbot.sevasvpn.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=newbot.sevasvpn.ru

 

 

Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • USt-IdNr.: DE221734518

 

Errors, ideas, questions? Use the Contact form • A project using Server-Daten - Web Database solutions