Dataweaz

telemach.si

Summary

Registrar
TELEMACH d.o.o.
Status
ok
Created on
January 4, 2000
Expires on
May 5, 2029
Name servers
ns3.telemach.si, ns1.telemach.si, ns2.telemach.si
Mail servers
sputnik.ugbb.net, apollo.ugbb.net

Spoofing protection (DMARC)

Monitoring

E-mails spoofing this domain are only reported, not blocked.

DMARC tells mail servers what to do with an e-mail that claims to come from telemach.si but fails SPF and DKIM checks.

Policy
Monitoring
Subdomain policy
Monitoring
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
[email protected]
Failure reports
—

Record

v=DMARC1; p=none; pct=100; rua=mailto:[email protected]

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for telemach.si.

RuleValueResult
ip4217.72.64.25Allowed
ip4217.72.64.24Allowed
aapollo.ugbb.netAllowed
asputnik.ugbb.netAllowed
asmtp4.telemach.netAllowed
includespf.protection.outlook.comAllowed
all—Rejected

Top-level DNS lookups: 4 of 10 allowed

Record

v=spf1 ip4:217.72.64.25 ip4:217.72.64.24 a:apollo.ugbb.net a:sputnik.ugbb.net a:smtp4.telemach.net include:spf.protection.outlook.com -all

E-mail signing (DKIM)

DKIM keys published by telemach.si under the most common selectors. Other keys may exist under selectors specific to each sending service.

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 2048 bitsActive
selector1Microsoft 365RSA 2048 bitsActive

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to telemach.si arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from telemach.si was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @telemach.si address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

telemach.si  MX  10 mx1.telemach.si.
telemach.si  MX  20 mx2.telemach.si.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.telemach.si.
Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .
An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

telemach.si  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1
Identifies the record as an SPF policy. It must come first.
ip4, ip6
Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx
Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include
Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all
Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.telemach.si, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.telemach.si  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1
Protocol version. Optional but recommended, in which case it must come first.
k
Key algorithm: rsa, the most common, or ed25519.
p
Public key, base64-encoded. An empty value means the key has been revoked.
t
Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.telemach.si, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.telemach.si  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1
Identifies the record as a DMARC policy. It must come first.
p
Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp
Subdomain policy. Without it, subdomains follow the domain's policy.
rua
Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf
Address that receives detailed failure reports, message by message. Few providers still send them.
pct
Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf
DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of telemach.si

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

ServerIP address
ns3.telemach.si213.143.67.125
ns1.telemach.si213.143.65.11
ns2.telemach.si162.159.48.178

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @telemach.si addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

PriorityServerIP address
10sputnik.ugbb.net213.143.80.39
10apollo.ugbb.net217.72.64.45

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.telemach.si.

NameContent
telemach.sipinterest-site-verification=97af7a8744e42a028119d8a9096ae413
telemach.sigoogle-site-verification=95aS4BrUNFm-EPubtCyGEmUAr5kQsXmVj0fW6taAdY8
telemach.si_8ekjdcsl3cqgtofm2wkojugn2ellryf
telemach.siMS=ms11139875
telemach.sifacebook-domain-verification=zzoassqhdtzo4xkybedaw7ci95x7b1
telemach.sica3-433fc0c878834bdc89ea03993070b719
telemach.siopenai-domain-verification=dv-jMM1kjomAb2z6D7rTQCVTZ54
telemach.siciscocidomainverification=607a043bdb39cefe5b1840bf10983a44d19dbdbf71aa125319f9ffeacdaff72c
telemach.si_6aunf60rmlnt7k654z56d2dailr17ms
telemach.siMS=741C386D372EA234467142F1F819560CAC24F634
telemach.sica3-45693e6902b0473cafa372ef2d8ec05b
telemach.siv=spf1 ip4:217.72.64.25 ip4:217.72.64.24 a:apollo.ugbb.net a:sputnik.ugbb.net a:smtp4.telemach.net include:spf.protection.outlook.com -all
_dmarc.telemach.siv=DMARC1; p=none; pct=100; rua=mailto:[email protected]
google._domainkey.telemach.siv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAiFTjVwNPL1zaLkNG2xL6sKcCIzfTA+Kw66wdlrsvnLmdfYI/XfrJ4Eh1u33d3uRWwfgHt6Dnaa7RiH8IUgW1YnyWrKJTKvtV2JhwUwpHoE7njC27Od/aldFPvUY6kpLfxmq3LaDMG+oMCYvv8sLT56rtEtbhmyvYVMET9JaeGpps/47HyI5F/cQzPlAYQ+4VIUBXcbOA4SireQmRvWFuKTN0H00vFH+B81VFir1n6EPI5Gnl7a6++jFhMqz8T2nphqKlZHILgdztTMiQFT2x2DsRVlboTt+vwFdEWSWrVkVHMrd7F7TrtmYPtA5McKcjXBDZfHUu8JWprm3u0TXvgQIDAQAB;
selector1._domainkey.telemach.siv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA7/VXZ4yG7+ZIDtRad+wEMhlBm8k+hY9Kq+uoYyPKbRzZG2YXVI+b9YAIUSfBJ1OygeOM8ZZ/l9FqWscrSpbMLlF8YHEMnCiT+pMITi3oB8/HeSQeT2dC9/Pjw4Quntve+Uy8JUny9NMwhotbyVH5knfqCbMDMG3lnsORr8aoBOfTUN9zjUUU+ZOGTuMQeW7Dt/Es42t418GTHsZJzjYP1usw7KJVsMIA2ijnicKgJu/p/++iGXv4zMDGKAlKDexG/cvRalISCj0eutnTDNe61GyUdKDNKTGBf8hpFN7cVLK6mc29BQ2anru70xBRzHMcoxW6qBBo9Mkbuy8uE/hFQQIDAQAB;

Related IP addresses

IPv4 addresses used by telemach.si: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
162.159.135.36Website162.159.135.0/24
162.159.134.36Website162.159.134.0/24
213.143.67.125Name server ns3.telemach.si213.143.67.0/24
213.143.65.11Name server ns1.telemach.si213.143.65.0/24
162.159.48.178Name server ns2.telemach.si162.159.48.0/24
213.143.80.39Mail server sputnik.ugbb.net213.143.80.0/24
217.72.64.45Mail server apollo.ugbb.net217.72.64.0/24
217.72.64.25Authorized by SPF217.72.64.0/24
217.72.64.24Authorized by SPF217.72.64.0/24

WHOIS of the domain telemach.si

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% This is ARNES whois database
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Rights restricted by copyright.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% The WHOIS service offered by Arnes, .si Registry, is
% provided for information purposes only. It allows persons
% to check whether a specific domain name is still available
% or not and to obtain information related to the registration
% records of existing domain names.
%
% This WHOIS service accepts and displays only ASCII characters.

% By submitting a query to our WHOIS lookup service, you agree
% to the restrictions on the use of WHOIS and WHOIS data as follows:
%      o You may not allow, enable or otherwise support
%        the transmission of unsolicited, commercial advertising
%        or other solicitations, whether via email or otherwise;
%      o You may not use the information to target advertising
%        in any possible way;
%      o You may not cause inconvenience the domain name holders
%        in any possible way by sending them messages
%        (whether by automated, electronic processes capable of
%        enabling high volumes or other possible means);
%      o You may not copy, extract and/or publish contents
%        of the WHOIS database.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

domain:		telemach.si
registrar:	TELEMACH d.o.o.
registrar-url:	http://domene.telemach.si
nameserver:	ns1.telemach.si (213.143.65.11)
nameserver:	ns2.telemach.si (162.159.48.178)
nameserver:	ns3.telemach.si (213.143.67.125)
registrant:	G50468
status:		ok
created:	2000-01-04
expire:		2029-05-05
source:		ARNES

Domain holder:
NOT DISCLOSED

Tech:
NOT DISCLOSED

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Full domain details are available here http://www.registry.si
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% Query time: 1587 msec
% WHEN: Sat Oct 03 04:40:17 UTC 2026