Skip to content

Hostname

tesamedical.ro

Last fetched

tesamedical.ro resolves to 188.213.21.239, announced in 188.213.20.0/23 by Cyber_Folks-RO-DC_CLJ - Cyber_Folks SRL in RO. tesamedical.ro is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · tesamedical.roRouting diversity2.4/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.6/10canon.whisper.security/host/tesamedical.ro

Resolution chain

IPv6 resolution

No AAAA record for tesamedical.ro is recorded in WhisperGraph.

Attribution

cyber folks

ORIGIN_AS

WHOIS identity

Registrar
registrar:cyber_folks s.r.l.

Subdomains

Subdomain
cpanel.tesamedical.ro
cpcalendars.tesamedical.ro
cpcontacts.tesamedical.ro
mail.tesamedical.ro
mktr.tesamedical.ro
webdisk.tesamedical.ro
webmail.tesamedical.ro
www.tesamedical.ro

Showing 8 of 8 subdomains (8 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • ns1.cyberfolks.ro
  • ns2.cyberfolks.ro
  • ns3.cyberfolks.ro
  • ns4.cyberfolks.ro
  • ns1.tlh.ro
  • ns2.tlh.ro

MX records

  • mail.tesamedical.ro

SPF policy

  • ip: 128.140.225.2/32
  • include: amazonses.com
  • include: spf.antispamcloud.com
  • include: spf.mxserver.ro
  • a: tesamedical.ro
  • mx: tesamedical.ro
  • ip: 185.171.185.104
  • ip: 77.81.165.204
  • ip: 95.214.132.32

Threat-feed evidence

History

Related pages

Pivot from tesamedical.ro into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "tesamedical.ro"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.