Dbsr.dk has a total of 15 DNS records. In the server records, it appears to be registered with the IP address 94.143.9.51 in Denmark, Central Jutland, Skanderborg, Europe/Copenhagen with the information belonging to DANDOMAIN The domain was registered on N/A, and the expiration date appears to be on N/A. When checked on , the website is still online. According to Siteadvisor, visiting dbsr.dk is safe.
Robot | Path | Permission |
---|---|---|
Google Bot | / | |
Bing Bot | / | |
Baudi Spider | / | |
Yandex Bot | / |
Title | N/A |
Description | N/A |
Keywords | N/A |
Website | dbsr.dk |
Host IP | 94.143.9.51 🇩🇰 |
Location | Skanderborg, Denmark |
Created | N/A |
Expires | N/A |
Owner | N/A |
Hosting Company | DANDOMAIN |
Registrar | N/A |
IPs | 94.143.9.51 |
DNS |
|
Host | Type | TTL | Data |
---|---|---|---|
dbsr.dk | A | 3600 | IP/Target: 94.143.9.51 |
dbsr.dk | NS | 3600 | Target: ns2.dandomain.dk |
dbsr.dk | NS | 3600 | Target: ns.dandomain.dk |
dbsr.dk | SOA | 3600 |
MNAME: ns.dandomain.dk RNAME: hostmaster.dandomain.dk Serial: 2025010604 Refresh: 14400 Retry: 3600 Expire: 1209600 Minimum TTL: 300 |
dbsr.dk | MX | 3600 | IP/Target: aspmx.l.google.com |
dbsr.dk | MX | 3600 | IP/Target: alt1.aspmx.l.google.com |
dbsr.dk | MX | 3600 | IP/Target: alt4.aspmx.l.google.com |
dbsr.dk | MX | 3600 | IP/Target: alt2.aspmx.l.google.com |
dbsr.dk | MX | 3600 | IP/Target: alt3.aspmx.l.google.com |
dbsr.dk | TXT | 3600 | TXT: _globalsign-domain-verification=3T-Js0W3jHoIkouggq_hulkpamUIQqmyL9GB28Q_l0 |
dbsr.dk | TXT | 3600 | TXT: 89OWZOi |
dbsr.dk | TXT | 3600 | TXT: google-site-verification=OLM-iDJ_FTIh5kNGlilUlZRM79aLetjyTNDKfg5X5VI |
dbsr.dk | CAA | 299 | Value: mailto:report-abuse@globalsign.com |
dbsr.dk | CAA | 299 | Value: globalsign.com |
dbsr.dk | CAA | 299 | Value: letsencrypt.org |
0: HTTP/1.1 403 Forbidden Content-Type: text/html Server: Microsoft-IIS/8.5 X-Powered-By: ASP.NET Date: Sat, 01 Feb 2025 03:53:07 GMT Connection: close Content-Length: 1938 |
Error: Monthly quota exceeded. Consider upgrading your subscription or wait until the API renew date. |