nspk.ru
The domain nspk.ru answers at IP address 194.190.0.23. Mail for nspk.ru goes through 2 servers; the highest priority one is relay01.nspk.ru. It also publishes 21 TXT records, used to verify domain ownership with external services and to configure mail security through SPF, DKIM and DMARC.
A A records
- 194.190.0.23 178s
MX MX records
- 25 relay01.nspk.ru 18556s
- 25 relay02.nspk.ru 18556s
NS NS records
- ns04.nspk.ru 21600s
- ns03.nspk.ru 21600s
- ns01.nspk.ru 21600s
- ns02.nspk.ru 21600s
TXT TXT records
- rYtK3IG5M/VglLZjmXOptDuKRoLVZ0Z0+xdAU20cGmo= 21600s
- TdhxbdhfnbHSND67484851 21600s
- jsdfhkjweb4t44JHNAKJSF345kjgf 21600s
- webinar-verification=40fad0e2e9fd4421200186c5c16b4871142345243644b73831bc36b526f5c2ee 21600s
- sdjfhkerjh3kjhtjdsjfhKLAJKLFH34 21600s
- easm-verification=KzdsepQEG0Nm3r5h2bPN2EZUaeNLewnF 21600s
- v=spf1 include:devinosender.com include:spf.unisender.com include:spf.prmta.net mx ip4:195.208.109.63 ip4:212.41.7.191 ip4:212.233.99.154 ~all 21600s
- dsfkdfj2ooo24isif12sjafsidhfo 21600s
- sojsddjfija1paoso4jpo3vdfo2ijdf4 21600s
- oijsdiofjsiofjio132ksajfdifo 21600s
- sdgjds54LKJKNKH 21600s
- dsfjhrkg34LKJSdgekjllLKDSLSWE66 21600s
- HARICA-HrqgGz2O5c0xJVTycAq 21600s
- sdpofksdok239dsfio123dfosk 21600s
- MS=D1E7C666B7A121BA157A160E1B913E6864E1202A 21600s
- unisender-go-validate-hash=501f2a5c8d916e0a23ac5213b381106f 21600s
- a7ee40a2-5ef9-449a-846e-7d03ae1a88ba 21600s
- sdjfhkjthj3k4htk34htj34khtgkjerhhgk 21600s
- 0fd879e5-03f9-4d74-8fb5-6d6f1929674f 21600s
- mailru-verification: 6f7dc33d1db62aca 21600s
- google-site-verification=O2chN_5pWMfW5ZubeZonQjWnYHugfnfYbV6PJdTbB80 21600s
SOA SOA records
- ns01.nspk.ru 21600s
What each record means
- A and AAAA: the server IP address, in IPv4 and IPv6.
- MX: the servers that receive the domain mail. The number is the priority; the lowest is tried first.
- NS: the name servers, which have the final say over the domain DNS.
- TXT: free text. Mostly used for SPF, DKIM and DMARC, and to verify ownership with third parties.
- TTL: how many seconds the record may be cached before asking again.
Checked 3 hours ago.